Upgrading Digital Hive on Windows to the 2024.3 Release

Upgrading Digital Hive on Windows to the 2024.3 Release

Overview

The 2024.3 Digital Hive release brings a lot of new capabilities to the market. In order to deliver some of the new features, changes to the underlying technology stack that underpins the Digital Hive solution had to be made. The 2024.3 release includes modernization to both PostgreSQL (Digital Hive Content Store) and ElasticSearch (provides the search capabilities). Although a lot of effort went in to upgrading the components and to minimize the effort required to upgrade existing Digital Hive implementations, there are some additional post-installation steps that must be performed to successfully migrate existing applications to the new 2024.3 release.

Installing a new instance of Digital Hive on Windows does not require any special installation considerations, and the Digital Hive Installation and Configuration Overview article can be followed.

Ensure that a recent backup of the Digital Hive server has been completed and is available. Because the upgrade requires a complete re-indexing of content, it is suggested that the upgrade be performed off hours and with enough lead time to complete the indexing of the content.

Installation steps

  1. Download the Digital Hive Installer DigitalHive-2024.3_win-x64.zip to the server
  2. Extract the file to a directory, in this example C:\DHInstaller
  3. In File Explorer, navigate to where you extracted the file in step 2. In this example, C:\DHInstaller\DigitalHive-2024.3-win-x64
  4. Open the DigitalHive-installer-win-x64 directory
  5. Right-click setup.exe
  6. Select run as Administrator
  7. When you see this, click More info
  8. Click Run anyway
  9. Click Yes and you should see the installer UI

  10. Click Next
  11. Enter Licensee name and License Key that were provided to you

  12. Click Next
  13. Select I accept the terms of this license agreement

  14. Click Next
  15. When prompted for an installation type, select Upgrade

  16. Click Next
  17. If you're upgrading a full installation of Digital Hive, select Full application

  18. Click Next
  19. Browse to where Digital Hive is currently installed, the default is C:\DigitalHive

  20. Click Next
  21. A pop-up with appear to inform you that some post-installation steps are required

  22. Press OK. Pressing Cancel will take you back to the previous screen to choose an installation directory
  23. Leave the default port of 7070 or change it for the Digital Hive IQ  (machine learning) component

  24. Click Next and the installation of the upgrade will begin
  25. When the installation process completes, a pop-up summary will be displayed reminding you about the post-installation steps that are required to complete the upgrade

  26. Click Next to end the installation process

Post-installation upgrade steps

The original post installation steps can be found in the <install_directory>/ContentStore/pg-upgrade/README-BundledContentStoreUpgrade.md directory. Using the steps in this article will provide more guidance, context, and clarity than what is in the README file.

As part of the upgrade process, a newer version of PostgreSQL is bundled with this release of Digital Hive in addition to the pre-upgrade version. In order to complete the Digital Hive upgrade please follow the instructions below to import your existing Digital Hive Content Store database from the old version of PostgreSQL to the new version of PostgreSQL.

Before you begin, verify that you have sufficient disk space to perform this upgrade. In order to import the old Content Store database into the new version of Postgres, you will need roughly double the space consumed by the old Content Store. The old Content Store is NOT deleted during the import (hence the temporary requirement for more disk space). To determine the amount of space consumed by the old content store, examine the properties of the <install_directory>/PostgreSQL directory. For example, if the folder size is 1GB ensure that more than 2GB of free disk space is available.

The next step in the process will be to start the migration of the Content Store data. These are the activities that will be completed as part of this task.
  1. Initialize the data directory for the new Content Store
  2. Verify that the old database and new database are compatible by executing some tests
  3. Importing the old database content into the new database
  4. Updates the Windows service to control the new database

The data in the old Content Store will **NOT** be modified during the upgrade. After the successful completion of the steps in this section, there will be two copies of the Digital Hive Content Store:
Old Content Store (inactive state) in the <install_directory>/PostgreSQL folder and the New Content Store (active) in the <install_directory>/ContentStore folder


Stop the Digital Hive services that are currently running.

  1. Open the Services panel and select the DigitalHive - node1 service
  2. Click Stop
  3. Select the DigitalHive Content Store service
  4. Click Stop
  5. Select the DigitalHive-IQ-Server service
  6. Click Stop
  7. Select Elasticsearch 7.17.16 (DigitalHive_9200) service
  8. Click Stop

Make sure to launch the Windows PowerShell application and NOT the Windows PowerShell ISE.

  1. Using the Windows search icon, locate the Windows PowerShell application

  2. Launch Windows PowerShell as an administrator
  3. Change the working directory to <install_directory>\ContentStore\pg-upgrade using the following command (with the C:\DigitalHive as the install directory):
    Set-Location -Path  "c:\DigitalHive\ContentStore\pg-upgrade"

  4. Execute the upgrade-dh-repository script by executing the following command: .\upgrade-dh-repository.ps1
  5. This will start a series of activities that you must wait to complete
  6. You will then be prompted for the old PostgreSQL content store password. This was defined when you first installed Digital Hive. If you don't have access to the password, you can press CTRL-C to exit the script and then manually run the last command later when you have the password
When the script stops running, if you're unable to type in your password or the PowerShell window won't accept any input, chances are that the Windows PowerShell ISE application was launched instead of the Windows PowerShell application. Terminate the PowerShell session and run the remaining commands manually. 

If the last steps in the script did not complete and need to be run manually, with the PostgreSQL password in hand, open a Windows command prompt:
  1. Type cd c:\DigitalHive\ContentStore\bin (change the statement to reflect your installation path)
  2. Press Enter on the keyboard
  3. Type vacuumdb.exe -U postgres --all --analyze-in-stages
  4. Press Enter on the keyboard

Start the remaining Digital Hive services that are currently stopped.

  1. Open the Services panel and select the DigitalHive - node1 service
  2. Click Start
  3. Select the DigitalHive-IQ-Server service
  4. Click Start
  5. Select Elasticsearch 7.17.16 (DigitalHive_9200) service
  6. Click Start
This process will kick off a brand new indexing of all content systems (based on the configured mount points). Based on current indexing job durations, Digital Hive will not display the entire content catalog until the indexing has been completed. 


After the upgrade, the Digital Hive installation should be verified to determine if everything is functioning as expected with the new Postgres version. In order to do this, launch Digital Hive as normal, and go through the application to verify that everything looks good. Once the application has been verified that the Digital Hive data was cleanly imported into the new Content Store, some configuration parameters need to be adjusted, and then the old Content Store can be archived to a location outside of the Digital Hive installation (if desired). 

  1. On the Digital Hive Windows server, navigate to the <install_directory>/DigitalHive/app/node1/Tomcat/conf directory
  2. Open the theia.properties file in a text editor
  3. Locate these two entries

  4. Change the current values to reflect the new Content Store path

  5. Save the changes to the file
  6. Restart the DigitalHive - node1 service
This is an optional step, but if you would like to maintain a backup of the original database, and free up some disk space, feel free to complete the step.

  1. Archive (zip) the <install_directory>/PostgreSQL directory old Content Store files)
  2. Copy the zip file to an external archive folder
  3. Delete the <install_directory>/PostgreSQL directory







    • Related Articles

    • Upgrading Digital Hive on Linux to the 2024.3 Release

      Overview The 2024.3 Digital Hive release brings a lot of new capabilities to the market. In order to deliver some of the new features, changes to the underlying technology stack that underpins the Digital Hive solution had to be made. The 2024.3 ...
    • What's New in the 2024.3 Digital Hive Release

      This articles details the new product features, enhancements, and resolved issues, that were included as part of the Digital Hive 2024.3 release. New Features & Enhancements Upgraded versions of PostgreSQL and ElasticSearch This release of Digital ...
    • What's New in the 2024.1 Digital Hive Release

      This articles details the new product features, enhancements, and resolved issues, that were included as part of the Digital Hive 2024.1 release. New Features & Enhancements Flyout button The Flyout button element is a great way to provide contextual ...
    • What's New in the 2024.2 Digital Hive Release

      This articles details the new product features, enhancements, and resolved issues, that were included as part of the Digital Hive 2024.2 release. New Features & Enhancements Control Center - Search tab Search is a very powerful use case within ...
    • Installing Digital Hive 2024.3 on Linux

      Overview The 2024.3 Digital Hive release brings a lot of new capabilities to the market. In order to deliver some of the new features, changes to the underlying technology stack that underpins the Digital Hive solution had to be made. The 2024.3 ...