Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel3
indent16px
excludeIntroduction|Contents

...

Upgrading to 4.12.4.904 from 4.12.3.900 (MongoDb V7.0)

Database Upgrade

This version has no new features and is intended only to upgrade the database version from V6.0 to V7.0.

Note

Please be aware of the following restrictions when upgrading to this release:

  • You can only upgrade to this version from 4.12.3.900. Because of the database requirements all upgrades must happen in sequence.

  • You must have started the installation of 4.12.3.900 at least once before upgrading to this version. Please see the note below on the requirements for starting a system at least once.

Upgrading to 4.12.3.900 from 4.12.2.896 (MongoDb V6.0)

Database Upgrade

This version has no new features and is intended only to upgrade the database version from V5.0 to V6.0.

Note

Please be aware of the following restrictions when upgrading to this release:

  • You can only upgrade to this version from 4.12.2.896. Because of the database requirements all upgrades must happen in sequence.

  • You must have started the installation of 4.12.2.896 at least once before upgrading to this version. Please see the note below on the requirements for starting a system at least once.

Upgrading to 4.12.2.896 from 4.12.1.893 (MongoDb V5.0)

Database Upgrade

This version has no new features and is intended only to upgrade the database version from V4.4 to V5.0.

Note

Please be aware of the following restrictions when upgrading to this release:

  • You can only upgrade to this version from 4.12.1.893. Because of the database requirements all upgrades must happen in sequence.

  • You must have started the installation of 4.12.1.893 at least once before upgrading to this version. Please see the note below on the requirements for starting a system at least once.

Starting an Installation at Least Once

To ensure an installation has been started at least once you must:

  1. Ensure all databases have been upgraded with the version you are trying to run.

  2. Ensure at least one of the Management Servers has been upgraded, however if you choose to only update one you should leave the other server deactivated.

  3. Ensure all database servers are running.

  4. Ensure the UI application is upgraded.

  5. Start one or more Management Servers and ensure it starts correctly.

  6. Verify that the system has started correctly by logging in through the client UI.

    1. Optionally you can also check the Management Server logs to ensure the upgrade did not generate any errors.

  7. Assuming everything has started correctly and the log showed no errors, you can stop all services and upgrade to the next version.

Upgrading to 4.12.1.893 (MongoDb 4.4)

Prerequisites

This release includes version 4.4 of the MongoDb database server. This version requires the Visual Studio C++ 2019 x64 redistributable library. Technically this has been part of the Witness pre-requisites since the release of 4.11, however we recommend this is checked before installing Build 1099. Please see Software Prerequisites for more information.

Info

Although the minimum requirement is C++ 2019, the recommended redistributable library is now Visual Studio C++ 2015-2022 x64. This will provide support for the upcoming releases which will all have newer versions of the MongoDb server.

.NET 8 Upgrade

This version is built on the latest Microsoft .NET technology stack. All necessary support files are shipped with the product so additional action is required, however be aware that .NET 8 is only supported on the following versions of Windows:

  • Windows 10 Build 1607 and newer.

  • Windows 11 Build 22000 and newer.

  • Windows Server 2012 and newer.

Database Authentication

Database authentication is supported in this release. If you need to implement it then please refer to Database Authentication. All configuration associated with the database authentication is done after installation.

Log Rotate

This version now automatically installs a Windows Scheduler Task to rotate the MongoDb logs every 24 hours. It is strongly recommended that any existing logs associated with older methods of log rotation are deleted before the task first runs to avoid any potential conflicts and confusion.

Info

Note that the Log Rotate task requires the necessary password details to access the database once authentication is enabled. Configuration of the task is covered in the Database Authentication documentation.

Upgrading to 4.12.0.879

Code Signing Certificate

...