The information on this page applies to updating to Enterprise Studio 4 release 21 September 2020 or newer. If you are updating to an older version, please contact BiZZdesign support.
Team Server is now called HoriZZon Server. While the new name is being implemented in the software and on the Support pages, the old name may still be visible in places until the process is completed. See also Team Server is now HoriZZon Server.
The instructions on this page apply to updating an existing on-premise installation, and to the latest release of Enterprise Studio. For a new on-premise installation of Enterprise Studio, please refer to Enterprise Studio and HoriZZon Server installation .
Depending on your situation, perform one or more of the following actions to update to a new Enterprise Studio release. D etermine 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
The latest installer file(s) can be downloaded from the BiZZdesign Support site.
Updating the HoriZZon Server
Always update the HoriZZon Server BEFORE updating Enterprise Studio.
Always create a backup of your database before updating the HoriZZon Server.
Depending on which version you are updating from, release-specific actions may apply. Before updating the HoriZZon Server, please refer to Enterprise Studio release-specific required actions.
Follow the procedure that is applicable to your situation:
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.
Steps:
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.