Upgrades
Helix Search 2024.2 and earlier: You must upgrade to Helix Search 2024.3 to migrate the index to the new index structure before upgrading to the latest version of Helix Search, see Upgrading Helix Search in the Helix Core Search Developer Guide. If you skip the Helix Search 2024.3 upgrade step and upgrade directly to the latest version of Helix Search, you must manually index all of your files from Helix Search, this can take a very long time, especially for larger systems. See Index Helix Search in the Helix Core Search Developer Guide.
When you upgrade to Helix Search 2024.3, Helix Search automatically migrates your index to the new index structure. While the migration is happening, the Elasticsearch Hosts service status will display In Progress on the Helix Search Service Status page, see View status. When the migration is complete, the Elasticsearch Hosts service status will change to Success and you can upgrade to the latest version of Helix Search. The time taken for the migration depends on the size of your index, it can be as short as a few minutes for a small index and hours for a larger index.
Helix DAM is built on top of Helix TeamHub. To install Helix DAM, you use the Helix TeamHub packages.
Helix DAM is shipped as a native operating system package, like .rpm or .deb, which greatly simplifies upgrades.
Upgrading Helix DAM is usually a zero-downtime operation and can be performed on a live system. Before upgrading, read the release notes for more information on any release specific upgrade instructions.
Download the TeamHub packages specific to the host operating system from Perforce's package repositories. After uploading the packages to the server, follow the commands below.
Alternatively, use the Perforce's package repositories directly to upgrade the packages instead of using the rpm -Uvh or dpkg -i commands below.
Standard
RHEL and CentOS upgrades
rpm -Uvh hth-X.X.X-stable.el8.x86_64.rpm
sudo hth-ctl reconfigure
Ubuntu
dpkg -i hth_X.X.X_amd64.deb
sudo hth-ctl reconfigure
Enterprise
When updating the Enterprise deployment type, the package install order (Web or DB) does not matter, as long as they are the same major version. Refer to the release notes for more information on the package install order.
Helix TeamHub DB
Upload the hth-db package to the server designated for Database role and update the package:
RHEL and CentOS
rpm -Uvh hth-db-X.X.X-stable.el8.x86_64.rpm
sudo hth-ctl reconfigure
Ubuntu
dpkg -i hth-db_X.X.X_amd64.deb
sudo hth-ctl reconfigure
Helix TeamHub
and Helix DAM Web
Upload the hth-web package to the server designated for Web application role and install the package:
RHEL and CentOS
rpm -Uvh hth-web-X.X.X-stable.el8.x86_64.rpm
sudo hth-ctl reconfigure
Ubuntu
dpkg -i hth-web_X.X.X_amd64.deb
sudo hth-ctl reconfigure
