Upgrading the server#
You can upgrade the HCL™ Launch server to incorporate to a later version. Always upgrade agents, agent relays, and the blueprint design server in addition to upgrading the server. Upgrading the server, agents, agent relays, and blueprint design server are each completed independently. Unless specified, upgrade the server before you upgrade the agents.
Upgrading the HCL Launch server can be performed using the same methods as an initial installation. However, there are a number of considerations that must be taken into account during an upgrade. Read the following sections before performing the upgrade. Also, check out this white paper: Upgrading to UrbanCode Deploy 7. The upgrade process is a complete replacement of the server.
Note: When you upgrade the server, installed plug-ins are upgraded to newer versions. The updated plug-ins are not necessarily compatible with an earlier version. When you upgrade, previous versions of the plug-ins are kept on the server. You cannot create processes with previous versions of plug-ins, but you can deploy snapshots that use the old versions of the plug-ins.
- Upgrading the server in interactive mode
To upgrade the server, stop the server and run the new installation program.
- 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.
- Releasing the VC LOB space
On upgrading to HCL Launch 7.0.5, the changes in the vc_persistent_record table reduces the amount of LOB storage space used by HCL Launch. You can optionally release the underlying LOB storage space. If you don't, the space will be reused when new records are added.
Parent topic: Upgrading and migrating