Home
Upgrading and migrating
Learn how to upgrade HCL Launch elements, including the server, agents, and how to migrate data.
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 agents in silent mode
You can upgrade agents by specifying the installation properties in a text file.

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 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 agents remotely
    Use the Upgrade action to upgrade agents that have a status of Upgrade Recommended or Upgrade Required. Always upgrade agents and agent relays in addition to upgrading the server.
  - Upgrading agents from the command line
    You can upgrade agents by stopping them and running the installation program for the new version.
  - Upgrading agents in silent mode
    You can upgrade agents by specifying the installation properties in a text file.
- Upgrading agents as services on Windows using command-line
  You can upgrade the currently running Deploy agent as a Windows service even though you initially didn’t install HCL Launch agent as a service during the installation process.
- 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

Upgrading agents in silent mode

You can upgrade agents by specifying the installation properties in a text file.

Before you begin

To ensure compatibility and optimal performance, run the same version of the HCL Launch server and agents. Server and agents of different versions may result in unexpected behavior. In such case, you must update or roll back the server and agents so that they run the same versions.
You must upgrade the server before you upgrade the agents. To upgrade the server, see Upgrading the server

About this task

To upgrade the agents in silent mode:

Procedure

From the new version of the server, download the agent installer for the new agent version.
- To download the installer, log in to the server and click the Help icon at the upper right of any page on the server, and click Tools. Then, click HCL Launch Agent, and download and extract the file.
- To find the installer on the server with the command line, go to the following location, and copy the file to the target computer: installation_folder/opt/tomcat/webapps/ROOT/tools/hcl-launch-agent-version.zip
Transfer the new agent installation package to the system that hosts the agent and extract the package.
Create a new or update the agent installation properties file.
For more information, see Agent installation properties. When you add the below property to the new agent properties file, the installer picks up the properties from the existing agent properties file:
```
locked/agent.home=current_installed_agent_path
```
Stop the agent.
Run the installation file with the install-agent-from-file.bat command on Windows™ or the ./install-agent-from-file.sh command on Linux™. Provide the properties file as a command-line argument.
On Windows™, if the properties file is named install.properties, type the following command:
```
install-agent-from-file install.properties
```
Restart the agent.

What to do next

On the server, click Resources > Agents and verify that the agent shows the new version.

Upgraded or installed agents are migrated to compact mode. Note that agents are updated to compact only if the agent is installed/upgraded on a platform that supports compact agents.