Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: date correction

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.


Excerpt

On this page:


Table of Contents
maxLevel1


Anchor
-565860581
-565860581
Update to Enterprise Studio 4

ReleaseSolution + required actions
8 7 April 2021No specific actions required.
1 April 2021No specific actions required.
29 March 2021No 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 2021No specific actions required.
4 February 2021

No specific actions required.

Excerpt

On-premise only: Final changes Team Server update procedure

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

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 2020No specific actions required.

12 November 2020


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

2 November 2020No specific actions required.
16 October 2020No specific actions required.
21 September 2020

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

7 September 2020No 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 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 ).
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 available

In 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 Server

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

  1. After installing the new Enterprise Studio, sign in to the new Team Server as a System Administrator user, and click Settings > License.

  2. In License key, enter the license key you have received, and click Apply to save the changes.

Continue upgrading custom configurations (if applicable) and migrating your model packages.

Customers running Enterprise Studio without a Team Server

Perform 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 11

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

29 May 2019

No specific actions required.

18 April 2019No specific actions required.
11 March 2019No specific actions required.
8 February 2019No specific actions required.
6 February 2019No specific actions required.
1 February 2019

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.

20 November 2018No specific actions required.
5 November 2018No specific actions required.
31 October 2018No specific actions required.
24 October 2018No specific actions required.
19 October 2018No specific actions required.

Update to earlier releases

ReleaseDetails

Anchor
-180904086
-180904086

Enterprise Studio 3.3.1

No specific actions required.

Anchor
release3.3
release3.3

Enterprise Studio 3.3

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:

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.

Anchor
-180707481
-180707481

Enterprise Studio 3.2

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.

Anchor
-1388496413
-1388496413

Enterprise Studio 3.1.7

No specific actions required.
Anchor
567818723
567818723

Enterprise Studio 3.1.6

No specific actions required.
Anchor
-1006159389
-1006159389

Enterprise Studio 3.1.5

No specific actions required.

Anchor
1714829795
1714829795
Enterprise Studio 3.1.1

No specific actions required.

Anchor
950221283
950221283
Enterprise Studio 3.0.4

No specific actions required.

Anchor
1332558307
1332558307
Enterprise Studio 3.0.2

No specific actions required.

Anchor
1714895331
1714895331
Enterprise Studio 3.0.0

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.

Anchor
931281379
931281379
Enterprise Studio 2.6.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.

Anchor
931084771
931084771
Enterprise Studio 2.5.0

No specific actions required.

Anchor
931150307
931150307
Enterprise Studio 2.4.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 29723462.

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.

Anchor
930953699
930953699
Enterprise Studio 2.3.0

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


ArchiMate® is a registered trademark of The Open Group.



Content by Label
showLabelsfalse
max6
showSpacefalse
titleRelated articles
cqllabel in ("release-notes","release","updating") AND label != "archive" and label != "troubleshooting" and space = "knowledge"