This release only includes a new HoriZZon and HoriZZon Server.

No specific actions required.

Release for limited amount of customers.

No specific actions required.

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.

On-premise only: Choose correct Team Server update procedure

This 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 from a release prior to Enterprise Studio 4 - 21 September 2020
• Updating from Enterprise Studio 4 - 21 September 2020

Updating to a new Enterprise Studio release - Update the Team Server

On-premise only: Changed Team Server update procedure

Due 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

No specific actions required.

12 July 2020

No specific actions required.

18 May 2020

On-premise only: New JDBC driver required for Team Server with MSSQL and integrated security

If 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:

• Open the teamserver.config.json file (in TeamServerHome folder), and in the database section check if singleSignOn is set to true:
  
  "singleSignOn" : true,

If set to true, you are using integrated security.

Steps:

1. Uninstall the old Team Server (step 1 of the procedure for updating the Team Server).
   
   
2. Download the file mssql-jdbc_auth.zip from https://github.com/microsoft/mssql-jdbc/releases/tag/v8.2.0.
   
   
3. Unzip the file, get the correct .dll file (32 or 64 bit), and place the file in the folder where the current JDBC file is located. It is a directory listed in the java.library.path system property. On Windows, this is set to the value of the PATH environment variable.
   Do not remove the old JDBC file, unless you are certain that it is not used by other applications.
   
   
4. Install the new Team Server (step 2 of the procedure for updating the Team Server ).

No specific actions required.

5 November 2019

11 July 2019

Cloud only: New licensing system available

This 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.

No specific actions required.

No specific actions required.

29 January 2019

On-premise + Hybrid: Enterprise Studio compatibility with Team Server

Enterprise 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.

Changes in software installation

As 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 authentication

If 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:

• On-premise installation: Configuring user synchronization and authentication with Azure Active Directory
• Cloud solution: Configuring Azure AD for hosted Team Server and HoriZZon

Changes in Active Directory configuration for user authentication

If 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.

Upgrade custom viewpoints and menu definitions

If 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.

1. Upgrade your current custom configuration to the new 3.2 tool configuration.
   
   
2. Migrate your Team Server model packages to your 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.

Commit outstanding changes before installing new tool version

If 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.

Commit outstanding changes before installing new tool version

Commit all outstanding changes in your Team Server model packages before updating to Enterprise Studio version 2.6.0.

Update Team Server configuration file if using HTTPS

If 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:

• https.keyStore
• https.keyStoreType
• https.keyStorePassword

For the new property names, please refer to Enterprise Studio release-specific required actions.

Convert TDM models to DMN

If 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.

Changed Team Server password storage requires re-entering storage place credentials

The 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).