Plan your upgrade of HCL VersionVault
Before you begin upgrading the HCL VersionVault and HCL VersionVault MultiSite software, learn about the upgrade process, complete any prerequisite tasks, and create an upgrade plan.
Important: If you are switching to the 64-bit
version of HCL VersionVault from the 32-bit version, you must first uninstall the 32-bit version of
VersionVault before installing the 64-bit version. Note that when you uninstall VersionVault, the
CCM.preserve directory is created. This directory contains any custom settings from the VersionVault
product that you uninstalled. When you reinstall the VersionVault product on the same machine, the
installation process discovers the CCM.preserve directory and presents options to let you use the
preserved settings from the previous installation for the new installation or to ignore
them.
This information provides a summary of how to prepare for and plan an upgrade for HCL VersionVault and HCL VersionVault MultiSite client and server software packages.
The following lists highlights changes from the previous release.
- Added Access Control List option for managing access to VOB objects. This option requires VersionVault VOBs formatted with schema 80 or higher, feature level 8.
- You must use Installation Manager, version 1.8.6 or later fix packs, or version 1.9.1 or later fix packs to install and upgrade packages. If Installation Manager has been configured for updates, the Installation Manager updates to the required version automatically. See the system requirements for VersionVault for the most up-to-date requirements.
- If you are upgrading VersionVault server features, make sure that you have the required version of IBM® WebSphere® Application Server components installed and configured before upgrading VersionVault. See the system requirements for VersionVault to know what version of WebSphere® Application Server components are required.
The following table summarizes the tasks for planning the upgrade and preparing your environment. Complete any prerequisite tasks before you upgrade the HCL VersionVault client and server software.
| Requirement | Client Server |
Information | Comment |
|---|---|---|---|
| Back up critical resources and configuration information | Client Server |
Back up environment resources | The software upgrade process overwrites any custom configuration files, including task schedules. Make sure you back up any customization that you want to save before you begin the upgrade process. |
| Review the release notes | Client Server |
See the release notes document provided with the product. | |
| Check the system requirements | Client Server |
Hardware and software requirements | This information includes operating system and file system support, basic hardware requirements, required operating system patches, and miscellaneous software support. |
| If you are using HCL VersionVault web applications, install WebSphere® Application Server and IBM® HTTP Server | Server | Prepare the WebSphere Application Server environment for HCL VersionVault web servers | This preparation is required for using VersionVault web applications and must be installed before you begin an upgrade. |
| Verify permissions on the .hostname file on the VOB | Server | The command protectvob does not work on the .hostname file. If you used the command for changes, you must manually change the .hostname file. | For more information about .hostname see: The VOB storage directory |
| Review important information to consider when planning HCL VersionVault upgrades and complete any necessary tasks required for your environment. | Client Server |
Important notes for planning HCL VersionVault upgrades HCL VersionVault MultiSite upgrade notes |
Upgrade the HCL VersionVault registry server host before any HCL VersionVault MultiSite replica server hosts. |
| Determine HCL VersionVault installation strategy | Client Server |
Enterprise software installation strategies | Planning for single-user and enterprise deployments. |
| Prepare for enterprise deployments | Client Server |
Preparing shared locations for an enterprise deployment | Prepare shared locations for user installations. |
| Optional. Plan support for ACL authorization of VOBs and VOB objects. | Client Server |
Planning support for ACL authorization of VOBs and VOB objects | |
| Optional. Plan for HCL VersionVault Remote Client installation | Client Server |
HCL VersionVault Explorer installation planning | |
| Optional. Plan for HCL VersionVault MultiSite installation | Server | HCL VersionVault MultiSite installation | |
| Configure licensing for your deployment | Server | Manage licensing for HCL VersionVault |