Compatibility across releases

If you plan to run different VersionVault versions on clients and servers in the same environment, review the client and server compatibility information.

HCL VersionVault operations require communication between multiple client and server components. For example, checking out a file in a dynamic view requires interaction between the client, the view server, and the VOB server. The client program runs on the developer workstation, which runs in a particular view on that workstation or elsewhere, and uses a particular VOB that is typically found on a dedicated VOB server host. If all clients and servers run the same VersionVault version, then the operations typically complete successfully. However, in environments that have different HCL VersionVault versions on different components, operations can fail if the VersionVault versions are not compatible.
Compatibility considerations
All versions of the HCL VersionVault software on the clients and servers in your environment must be compatible. When you consider compatibility issues, keep in mind these points:
  • You can avoid HCL VersionVault compatibility problems by deploying the same VersionVault version on all client and server components in your environment.
  • If you plan to upgrade the HCL VersionVault version on server and client components in your environment in phases, review the VersionVault compatibility information in technote 477019.

    Make sure that the HCL VersionVault version you are upgrading to is compatible with the versions that are installed on other components in your environment.

  • If you are using HCL VersionVault in a UCM environment, review the known issues in technote 477019.

    All compatibility issues in a UCM environment can be avoided by upgrading the server to a version that is at the same level or newer than the version that is installed on the client.