The 3 November 2022 release is the last version that supports Microsoft SQL Server for your Horizzon Server database. If you still use Microsoft SQL Server, you must migrate your database to PostgreSQL 14 to be able to use future versions . The 3 November 2022 release is the last version you can use to migrate. For more information and instructions, please refer to Migrating the Horizzon Server database from Microsoft SQL Server to PostgreSQL .
The instructions on this page apply to the on-premise installation of the Bizzdesign Horizzon platform for Windows. If you are using a Linux-based version of Horizzon, download the latest installation bundle including instructions from the Bizzdesign Support portal.
Depending on your situation, perform one or more of the following actions to update to a new software release. Determine which of the situations below applies to you, and follow the associated procedure(s).
Updating to a new release should only be done by application administrators who are familiar with installing and configuring software and databases.
Enterprise Studio and Horizzon Server are both running on premise
Download the new software: Enterprise Studio and Horizzon Server
Enterprise Studio is running on premise, Horizzon Server is running online
Download the new software: only Enterprise Studio
Enterprise Studio and Horizzon Server are both running online
Downloading the new software
Download the latest installer file(s) for the Windows version from the Bizzdesign customer portal.
Horizzon ServerUpdating the
The instructions apply to updating from the 20 December 2021 release, or newer and Windows-based. If you are updating from an older version or use a Linux-based Horizzon, please contact Bizzdesign Support for information.
Always update the Horizzon Server BEFORE updating Enterprise Studio. Depending on the version you are updating from, release-specific actions may apply. Please check this before updating the Horizzon Server.
Always create a backup of your database before updating the Horizzon Server.
Uninstall the old Horizzon Server and Worker
Stop the old Horizzon Server service by running the stopServer.bat and stopWorker.bat files located in the bat folder of the Horizzon Server installation. This is mandatory. It ensures that the Horizzon Server will have flushed all of its data into persistent storage and ensures this consistent data set is used by the Horizzon Server.
Uninstall the old Horizzon Server service by running the uninstallServer.bat and uninstallWorker.bat files located in the bat folder of the Horizzon Server installation.
Install the new Horizzon Server and Worker
Rename the current HorizzonServerHome folder to HorizzonServerHome-old.
Unzip the new Horizzon Server installer file to the location where the Horizzon Server must be installed. You are strongly advised to install the Horizzon Server at the root of the drive because the installation path cannot be longer than 49 characters, including the HorizzonServerHome installation folder. For example, C:\HorizzonServerHome.
If you have previously made changes to the wrapper.conf file, add these changes to the server.wrapper.conf file in the new Horizzon Server installation (located in the HorizzonServerHome\conf folder). Examples of changes may be the HTTP port, the java.exe location, and JVM memory. If you have made changes to the java.exe location, then also update the worker.wrapper.conf file.
- If you have previously made changes to the application.conf file, add the same changes to the file in the new Horizzon Server installation (located in the HorizzonServerHome\conf folder). Examples of changes may be the teamServiceUrl, secret key, and the SQL Server JDBC.
- Add the new Horizzon Server and Horizzon Worker services to the services by running the installServer.bat and installWorker.bat files located in the bat folder of the Horizzon Server installation. If you have previously added the Horizzon Server using an AD service account, use that account again.
- Start the new Horizzon Server and Horizzon Worker services by running the startServer.bat and startWorker.bat files located in the bat folder of the Horizzon Server installation. All data and users should be available again.
Updating Enterprise Studio
If you also use an on-premise Horizzon Server, always update the Horizzon Server BEFORE updating Enterprise Studio.
Close Enterprise Studio and the Activity Console before installing the new version of Enterprise Studio.
Install the new version of Enterprise Studio on the client computers. Please take note that the installer will completely remove the previous Enterprise Studio installation. Only in case of updating to a new major release (e.g., from ES 4 tot ES 5) you can select a different installation location, if desired. That can be done via Options on the first page of the installation wizard.
Upgrading to the new tool configuration
Upgrade to the new tool configuration and migrate your Horizzon Server model packages. Any customizations in your current tool configuration will automatically be transferred to the new configuration during the migration, provided that these customizations have been made using the Metamodeler. The migration is performed using the Metamodeler.
If your custom configuration includes any changes made outside the Metamodeler, do not perform the procedure below. Instead follow the procedure for manually upgrading the tool configuration and migrating model packages .
Upgrading to the tool configuration can only be performed by users with the Lead Designer role.
Enterprise Studio is not backward compatible. Once you have opened and saved a model in a newer version of the tool, the model should not be opened in an older version of the tool.
In Enterprise Studio, open a Horizzon Server model package that needs to be migrated, and go to File > Manage Package > Manage Configuration.
If the model package still has uncommitted changes, commit these pending changes first, or undo the changes (via Timeline > Undo Changes) before upgrading.
Click Upgrade configuration. A message appears informing you about the consequences of upgrading. If you want to start the upgrade, click Yes.
If upgrading is successful, the following message appears. Click OK . You are automatically redirected to the Commit page.
If upgrading is successful, but messages appear in the Messages window, you are not directly redirected to the Commit page. Please check these messages before deciding to commit the configuration changes in the model package.
If upgrading is not successful, the procedure is aborted.
On the Commit page, click Commit to commit the configuration changes (indicated by the icon).
Enter a version number of the configuration you have migrated to in the Remarks box. That way you will be able to see which configuration version you are working with in the model package's timeline.
Migration of the model package is now complete. The configuration changes will become available to other users participating on the model package. They need to update their copy of the model package to include the configuration changes.
If the migrated model package has projects based on it, these projects need to be updated with contributions from the master model package to include the configuration changes.
Users contributing to these projects can include the configuration changes in their copies of the project by updating their project with contributions from other users.