Upgrading the server in silent mode#

Use silent mode to upgrade without command-line prompts. To upgrade the server, stop the server, edit the properties file, and run the new installation program. These instructions apply to upgrades from versions 6.0 and later.

Depending on the version of HCL™ Launch you are upgrading, be sure to address these build-specific considerations.

Affected Build Consideration
6.1 and later If the server is using an HCL® JRE, upgrade the JRE to a version that is shipped with version 6.2 or later.
6.1 - HCL Launch servers and relays must be upgraded at the same time. Agents that connect through relays may not connect successfully until both server and relay are upgraded.
6.2.2 and later HCL Launch server and agent relays require a Java™ Runtime Environment (JRE) or Java Development Kit (JDK) version 8. After upgrading, these changes apply to the agent relays. Users might notice that some agent relays are no longer listed in the user interface even though they were able to view relays before the upgrade. The new version includes updated security controls. The agent relays are still available to the users. However, System Team administrators can assign agent relays to teams and set the View Agent Relays permission for roles so that appropriate users can see the agent relays in the user interface. Users can install and use agent relays. However, the relays are not listed in the user interface for the user until a System Team administrator assigns the agent relay to teams and sets the View Agent Relays permission.
6.1 - Ensure that all secure property values are obscured, the values of all properties in the history for existing deployments are obscured. In the deployment history for deployments that you run after you upgrade, only secure properties are obscured in the logs.
6.1 - New security features erase old component version import logs to hide secure information. If you want to keep the logs, in the installed.properties file, set the property com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip to True.
7.0.5 Upgrading to 7.0.5 enables compression of new VC entries that reduces the vc_persistent_record table growth rate. If you are using MySQL or MariaDB, then the upgrade may take longer due to the vc_persistent_record table changes. To avoid the delay on MySQL 5.6 or MariaDB 10.0 or later, run the following SQL statement before starting the upgrade: ALTER TABLE vc_persistent_record MODIFY persistent_data longtext null, ADD compressed_data longblob null, lock=none Note that you can run this command without shutting down the HCL Launch server. Attention: If the command fails, proceed with the upgrade and let the upgrade script make these changes. In such case, the upgrade requires downtime. It is recommended to run the command on a cloned HCL Launch database to get an estimate of downtime duration.

This task applies to upgrades of versions 6.1 or later. Contact HCL Launch support for all other versions.


During the upgrade, the contents of the appdata/patches directory (including all .jar files) will be appended with .off, preventing the existing test fixes from being loaded once the HCL Launch Server is started post-installation. All UI test fixes applied to the Tomcat directory will be wiped by the upgrade and will not be recoverable.

If a text fix received for a reported defect is not fixed in the upgraded version, you may need to open a Support Case to request a new build.

Note: Setting com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip to True is only effective upon upgrade. After upgrading, component version import logs are automatically cleaned up after 24 hours by default. Refer to Component Versions.

  1. If you have added custom keystores, certificates, or any other files to the server_install/opt/tomcat directory, back up those files before you upgrade. If you do not back up files that you have added to the server_install/opt/tomcat directory, those files are removed when the upgrade process runs.

  2. Download and extract the installation files for HCL Launch. These files are available for download from the HCL FlexNet Operations portal.

  3. Ensure that no application and generic processes are running.

    Open the Dashboard and confirm that no processes are running. If processes are running, you can wait for them to complete or by clicking Cancel in the same row as each process, cancel them. In versions and later, you can use the Message of the Day feature (Settings > System > General Settings > ****) to notify users of the planned upgrade, and request that they do not start new processes.

  4. Stop the server.

  5. Ensure that the server is stopped:

    1. Check to ensure that there is no file server.pid in the server_install/var folder.

    2. Check for running system processes.

      For example, on Linux™, you can use the netstat or ps commands. For example, if the server is running on port 8443, use the command netstat -nap | grep 8443. You can also run ps -ef | grep server and look for the server system process in the results.

    3. If any server processes are still running, stop them.

    If a server process is still running, when you install the new version, you see an error that says "A previously installed version of HCL Launch is running. Please shutdown the running HCL Launch and start the installation again."

  6. Back up the database.

  7. If you are upgrading from a version prior to version 6.2.2 to version 6.2.2 or later, upgrade the version of Java on the server to version 8 or later.

    See Changing or updating the JRE of servers.

  8. In the installation files, open the install.properties file in a text editor, and add the following line of code to the file:


  9. Ensure that the install.server.dir property is set to the directory where HCL Launch is installed.

  10. From the command line, run the server installer program.

    • On Windows™, run the install-server.bat file.
    • On Linux, run ./install-server.sh.
    • To install a FIPS-compliant server, add the switch -fips to the command, such as install-server.sh -fips.

      Note: If you install a FIPS-compliant server, cloud provisioning is not available. Your JVM connects to only FIPS 140-2 certified HCL providers.

    Depending on your system settings, you might need to run this file as an administrator.

  11. Start the server, and verify that the server is upgraded.

  12. Ensure that licensing is set up for the server.

    See License management.

  13. If you are upgrading the server from version or earlier to a version later than version, upgrade the encryption key strength.

    See Upgrading encryption key strength.

  14. Upgrade the agents.

    See Upgrading agents. If you are upgrading from a version before to version or later, you must upgrade agents that use Java plug-ins, including most source configuration plug-ins. If you do not upgrade the agents, they will throw an IllegalCharsetNameException exception that refers to the variable DS_SYSTEM_ENCODING.

If you are upgrading from version to or later, upgrade all agent relays to the current version. Agents that connect through relays may not connect successfully until both server and relay are upgraded.

Parent topic: Upgrading the server