Home
Upgrading and migrating
Learn how to upgrade HCL Launch elements, including the server, agents, and how to migrate data.
Testing an upgrade
Before you upgrade your production HCL Launch server, for best results, perform a test upgrade, verify the challenges you are facing, and resolve them before performing an actual upgrade.

Upgrading and migrating
Learn how to upgrade HCL Launch elements, including the server, agents, and how to migrate data.
- Testing an upgrade
  Before you upgrade your production HCL Launch server, for best results, perform a test upgrade, verify the challenges you are facing, and resolve them before performing an actual upgrade.
  - Testing upgrades on a cloned virtual machine
    You can perform a test upgrade of your production server that is hosted on a virtual machine (VM).
  - Testing upgrades on a cloned on-prem installation
    You can install a new HCL Launch server and then populate it with data from the production server.
- Upgrading the server
  You can upgrade the HCL Launch server to incorporate to a later version. Always upgrade agents, agent relays in addition to upgrading the server. Upgrading the server, agents, agent relays are each completed independently. Unless specified, upgrade the server before you upgrade the agents.
- Upgrading high-availability installations
  All servers that are configured for the HA feature must be on the same version. Thus, all servers must be upgraded at the same time.
- Upgrading agents
  In most cases, you upgrade agents from the server interface, but you can also upgrade the agents from the command line. Always upgrade agents and agent relays in addition to upgrading the server.
- Upgrading agent relays
  In most cases, you upgrade agents relays from the command line, but starting from 7.0.4.2 version, you can upgrade the server from the interface. Always upgrade agents and agent relays in addition to upgrading the server.
- Migrating the server database
  The server installation files include a script that migrates the server database from Derby to another database system. You can not migrate from any database other than Derby.
- Migrating the server to Kubernetes/Openshift
  You can migrate your HCL Launch server from an on-premises production installation to a containerized instance that runs in a Kubernetes or Openshift cluster.
- Migrating an existing IBM® installation to HCL Launch

Testing an upgrade

Before you upgrade your production HCL Launch server, for best results, perform a test upgrade, verify the challenges you are facing, and resolve them before performing an actual upgrade.

The process to test an upgrade requires you to manually clone the HCL Launch server that includes the filesystem, database, and application data (appdata) folder to a new instance.

In this section, you create a testing environment by cloning all or most of the production environment. You test an upgrade in one of the two ways:

Type 1: Cloning the production server hosted on a virtual machine (VM)
Type 2: Cloning the production server hosted on an on-premises installation