Below you can find the actions that need to be performed when updating your Enterprise Studio software to a specific release, and to which software solution the actions apply. The latest release is listed first.
On this page:
Update to Enterprise Studio 4
Release | Solution + required actions |
---|---|
7 April 2021 | No specific actions required. |
1 April 2021 | No specific actions required. |
29 March 2021 | No specific actions required. |
15 March 2021 | This release only includes a new HoriZZon and HoriZZon Server. No specific actions required. |
1 March 2021 | Release for limited amount of customers. No specific actions required. |
26 February 2021 | On-premise only: Different release dates for download files Although the Enterprise Studio and HoriZZon Server downloads for this release have different dates (26 Feb and 19 Feb), they are part of the same release. The release does not require any specific actions. |
17 February 2021 | No specific actions required. |
4 February 2021 | No specific actions required. The last phase of the on-premise Team Server and HoriZZon Server merge has resulted in final changes to the update procedure. From now on the installation bundle also includes a new component: the HoriZZon Worker. Various important background tasks are now executed by the HoriZZon Worker to allow for better scaling. Additionally, the new component enables an optional preprocessing step that improves initial loading of model packages/projects. If you are working with an on-premise Team Server, please carefully read the update procedure before you start updating to the new release. Determine from which Enterprise Studio release you are updating and choose the matching procedure: Updating to a new Enterprise Studio release - Update the HoriZZon Server Please take note that from now on Team Server is called HoriZZon Server. |
28 January 2021 | No specific actions required. |
23 November 2020 | No specific actions required. |
12 November 2020 | On-premise only: Choose correct Team Server update procedureThis release includes 2 update procedures for the on-premise Team Server. Determine from which Enterprise Studio release you are updating and choose the matching update procedure.
Updating to a new Enterprise Studio release - Update the Team Server |
2 November 2020 | No specific actions required. |
16 October 2020 | No specific actions required. |
21 September 2020 | On-premise only: Changed Team Server update procedureDue to the removal of the json configuration file from the Team Server installation bundle, the update procedure for the on-premise installation of the Team Server has changed. If you are working with an on-premise Team Server, please carefully read the procedure for updating the Team Server before you start updating to the new release. Updating to a new Enterprise Studio release - Update the Team Server |
7 September 2020 | No specific actions required. |
6 August 2020 | No specific actions required. |
12 July 2020 | No specific actions required. |
23 June 2020 | No specific actions required. |
28 May 2020 | No specific actions required. |
18 May 2020 | On-premise only: New JDBC driver required for Team Server with MSSQL and integrated securityIf you are working with an on-premise installation of the Team Server, using MSSQL, and using integrated security for the Team Server, you need to download a new JDBC driver for the Team Server before updating to the new version. If you are not sure whether you use integrated security, you can check it as follows:
Steps:
|
2 March 2020 | No specific actions required. |
24 January 2020 | No specific actions required. |
20 December 2019 | No specific actions required. |
5 November 2019 | On-premise only: New licensing system availableIn this release the new licensing system is available for the on-premise solution, and requires the availability of a Team Server, which acts a the licensing server. Customers running Enterprise Studio with a Team ServerAfter installing the new Team Server and new Enterprise Studio, and before upgrading any custom configurations and migrating model packages, perform the following instructions for registering your new license code:
Continue upgrading custom configurations (if applicable) and migrating your model packages. Customers running Enterprise Studio without a Team ServerPerform the procedure for installing a new Enterprise Studio with a Team Server to update to this release. Do not perform your regular update procedure. For instructions, please refer to Enterprise Studio and HoriZZon Server installation . On-premise only: Team Server requires Java 11As of this release the Team Server is no longer compatible with Java Runtime Environment (JRE) 1.8 or OpenJDK 8. You will need to update to Oracle JDK 11 or OpenJDK 11. OpenJDK11 can be downloaded here: https://github.com/ojdkbuild/ojdkbuild . Choose the 11 version. For easier installation, it is advised to download the MSI file. If you encounter any problems starting the Team Server after installing Java, please refer to Unable to start the HoriZZon Server after installing Java 11. |
23 October 2019 | No specific actions required. |
5 September 2019 | No specific actions required. Only available for the cloud solution. |
13 August 2019 | No specific actions required. Only available for the cloud solution. |
2 August 2019 | No specific actions required. Only available for the cloud solution. |
18 July 2019 | No specific actions required. Only available for the cloud solution. |
11 July 2019 | Cloud only: New licensing system availableThis release comes with a new licensing system that requires the availability of a Team Server, which acts a the licensing server. The release is only available for customers with the cloud solution Enterprise Studio Online. Customers with the cloud solution can continue working with the release. |
29 May 2019 | No specific actions required. |
18 April 2019 | No specific actions required. |
11 March 2019 | No specific actions required. |
8 February 2019 | No specific actions required. |
6 February 2019 | No specific actions required. |
1 February 2019 | No specific actions required. |
29 January 2019 | On-premise + Hybrid: Enterprise Studio compatibility with Team ServerEnterprise Studio versions older than 3.3 are not compatible with the Team Server of this 4 release. If you are running an on-premise Enterprise Studio version that is older than 3.3, and your Team Server is running on premise or online, you need to update your Enterprise Studio to the 4 release in order to be able to use the Team Server of this 4 release. |
20 November 2018 | No specific actions required. |
5 November 2018 | No specific actions required. |
31 October 2018 | No specific actions required. |
24 October 2018 | No specific actions required. |
19 October 2018 | No specific actions required. |
Update to earlier releases
Release | Details |
---|---|
Enterprise Studio 3.3.1 | No specific actions required. |
Enterprise Studio 3.3 | Changes in software installationAs of this release, you will be prompted to close all open applications during the installation of Enterprise Studio. If you leave applications open, unsaved data may be lost. Changes in Azure AD configuration for user authenticationIf your organization is using Azure Active Directory for user authentication in the Team Server and HoriZZon (if applicable), please read the following information. In Enterprise Studio 3.3 it is required to register a client application secret. If there is no secret registered, the Team Server will not be able to authenticate with Azure AD, and users will not be able to sign in to the Team Server and HoriZZon. To be able to retrieve the secret, a new BiZZdesign authentication application needs to be created in Azure AD. The secret, tenant ID, and client application ID of the new authentication app need to be registered on the Authentication settings page in the Team Server. For instructions please refer to the following:
Changes in Active Directory configuration for user authenticationIf your organization is using Active Directory for user authentication in the Team Server and HoriZZon (if applicable) and not using a keytab, please read the following information. In Enterprise Studio 3.3 Kerberos (Windows Integrated Authentication) requires a keytab. If you do not use a keytab yet, please make the necessary changes in your Active Directory configuration in the Team Server, otherwise users will not be able to sign in to the Team Server and HoriZZon. |
Enterprise Studio 3.2 | Upgrade custom viewpoints and menu definitionsIf you have custom viewpoint definitions and/or custom ArchiMate® menu definitions in your custom tool configuration, follow the steps below to successfully upgrade them to the new tool configuration.
If you only have custom viewpoint definitions, you are ready now. If you have custom ArchiMate menu definitions (located in "AbstractContainer-new-menu.xml" and "AbstractView-new-menu.xml"), open the ArchiMate metamodel of your new tool configuration in the Metamodeler, and recreate your custom menu in the "Menu definition" file. For instructions, please refer to the Metamodeler Guide. |
Enterprise Studio 3.1.7 | No specific actions required. |
Enterprise Studio 3.1.6 | No specific actions required. |
Enterprise Studio 3.1.5 | No specific actions required. |
Enterprise Studio 3.1.1 | No specific actions required. |
Enterprise Studio 3.0.4 | No specific actions required. |
Enterprise Studio 3.0.2 | No specific actions required. |
Enterprise Studio 3.0.0 | Commit outstanding changes before installing new tool versionIf you are updating from Enterprise Studio version 2.5.0 or lower to version 3.0.0, commit all outstanding changes in your Team Server model packages before updating to Enterprise Studio 3.0.0. This is not needed if you are updating from version 2.6.0 to 3.0.0. |
Enterprise Studio 2.6.0 | Commit outstanding changes before installing new tool versionCommit all outstanding changes in your Team Server model packages before updating to Enterprise Studio version 2.6.0. |
Enterprise Studio 2.5.0 | No specific actions required. |
Enterprise Studio 2.4.0 | Update Team Server configuration file if using HTTPSIf you are using HTTPS for your Team Server installation (using certificates), you need to update the Team Server configuration file when updating your Team Server for this release, because the configuration properties for HTTPS have changed. The following properties must be changed:
For the new property names, please refer to Enterprise Studio release-specific required actions. Convert TDM models to DMNIf you are working with the TDM (The Decision Model) functionality, you need to convert your existing models to equivalent DMN models in order to continue working with them. To do this, follow the instructions in Converting TDM models to DMN. |
Enterprise Studio 2.3.0 | Changed Team Server password storage requires re-entering storage place credentialsThe Activity Console no longer stores passwords to connect with the Team Server. It uses cookies instead. As a result of this existing storage places will fail to connect, because there is no cookie available yet. The Activity Console will also point this out by indicating that a specific storage place could not be synced. To resolve this, the user needs to update each storage place connection in Enterprise Studio by reentering the credentials for the storage place. The storage places can found on the Storage Places tab of the Enterprise Studio Options (File > Options). |
ArchiMate® is a registered trademark of The Open Group.