Skip to main content
Version: 15.1

New Features in ADOIT 15.1

ADOIT 15.1 is a feature update to ADOIT 15.0 LTS. It includes a number of improvements and new features that are listed below.

Furthermore, this update includes fixes for problems discovered since the release of ADOIT 15.0 LTS.

New Features for All Users

Share and Invite

Sharing repository content with other ADOIT users has never been easier! You can access the new Share button from everywhere with one click:

Share button

You can easily share links with multiple people. Just start typing a username or email address, and then choose the user you want to share with from the list that appears.

Share dialog

If the recipient is not an ADOIT user or has no email address associated, you need to enter the full email address. You can even add a personal message if you want.

note

For details, please refer to the section "Generate URL" in the User Manual.

Accessibility Improvements

We are committed to increasing accessibility for people with disabilities. We view accessibility as an ongoing effort and carry out accessibility tests at regular intervals. In ADOIT 15.1, we focused on improving keyboard navigation in several places and optimised alternative texts for buttons and icons.

New Features for Users of the ArchiMate Application Library

ADONIS Connector: Importing Processes Made Easy

We added a new ADONIS connector for importing processes from ADONIS into ADOIT. This new connector replaces the BOC Management Office Integration interface (MOI), which will be removed in a future release of ADOIT. 

ADONIS Connector

What does this mean for Users?

Here's what changes and what improves for ADOIT users who use this interface to import objects:

  • The synchronisation of objects between ADOIT and its sister product ADONIS is still triggered directly in the Connect Center.

  • Power users can dynamically set parameters for the next transfer. For example, it is possible to select the target group for importing objects.

  • When the transfer is started, BPM elements will be imported into ADOIT. In contrast to the MOI interface, EA elements will no longer be automatically sent to ADONIS.

  • When the synchronisation is complete, a synchronisation report appears. It provides detailed information on which objects were created, updated, deleted, and more.

note

For details, please refer to the section "Synchronise Objects with ADONIS" in the User Manual.

New Features for ADOIT Administrators

ADONIS Connector: Replacement for the MOI Interface

The new ADONIS connector enables importing objects from ADONIS into ADOIT. It serves as a replacement for the BOC Management Office Integration interface (MOI), which will be removed in a future version of ADOIT.

ADONIS connector configuration

The main focus in the development of the new ADONIS connector was to simplify setup and operation.

The configuration uses the Integration Framework (EXT_CONNECT). First, access to the REST API needs to be enabled on the ADOIT side so that ADONIS can retrieve data from there. Then, the data connector that will be used to connect to ADOIT is configured on the ADONIS side.

note

To use the ADOIT connector, you need ADONIS 14.1 or higher AND ADOIT 15.1 or higher.

For details, please refer to the section "Management Office Integration" in the Administration Manual.

Migration from an Earlier Version of ADOIT to ADOIT 15.1

Changes to Software Requirements

Please note the following changes to the software requirements for running ADOIT when migrating from previous versions:

  • Java Logging: Switch to Logback from Log4j

Due the recent well-documented security issues related to the usage of older versions of the log4j Java logging library, BOC Group has decided to switch to the alternative Java logging framework logback (https://logback.qos.ch/). A new standard logging configuration is delivered with the product. Custom logging configurations need to be migrated.

Migration from ADOIT 15.0 to ADOIT 15.1 (ArchiMate Library)

If you upgrade from ADOIT 15.0 to ADOIT 15.1, you do not have to create a new database and import a migration package if you are using the ArchiMate Library.

note

This approach is also valid if you are using an ArchiMate Library with changes in the metamodel.

If you are using ADOIT 15.0 with the ADOIT Standard Application Library or another specific library, read on here.

Prerequisites

  • You will need the installation package for a successful and complete migration.
  • Before you start the migration, we strongly recommend creating a backup of the database.

Migration

The migration consists of the following steps:

  1. Stop the ADOIT 15.0 application server and the Apache Tomcat web server.

  2. Export the library-specific component settings.

  3. Back up comments and deployment-specific configuration settings.

  4. Install ADOIT 15.1 according to the ADOIT 15.1 Installation Manual:

    a. Install the rich client for use as an application server and for using the Administration Toolkit.

    b. Install the web client to host ADOIT 15.1 as a web application.

  5. Start the ADOIT 15.1 Administration Toolkit and log in to the ADOIT database.

  6. Update the application library:

    • If you are using the ArchiMate Library: Databases created with ADOIT 15.0 can still be used with ADOIT 15.1. However, you will not have access to improvements in the ArchiMate Library. (Optionally) Update the library in the ADOIT database. A new version of the ArchiMate Library can be found in the folder "04 Sample Data\Library" in the installation package.

    • If you are using an ArchiMate Library with changes in the metamodel: Databases created with ADOIT 15.0 can still be used with ADOIT 15.1. However, you will not have access to improvements in the ArchiMate Library. (Optionally) Contact your ADOIT consultant to upgrade your application library.

  7. Import the library-specific component settings if you updated the application library.

  8. Migrate comments and deployment-specific configuration settings.

  9. Start the ADOIT 15.1 application server and the Apache Tomcat web server. If ADOIT 15.1 is working properly, you can uninstall ADOIT 14.0.

note

(Optionally) In case it did not already happen as part of the upgrade to ADOIT 15.0, you can transfer the users to the new standard system roles User, Reader and MM and Integration Administrator. For details, see Transfer Users to the New Standard System Roles.

note

For further information and details on the above steps, please refer to the Installation Manual and to the sections "Make a Manual Backup" , "Restore a Manual Backup" and "Update Library" in the Administration Manual.

Migration from ADOIT 14.0 to ADOIT 15.1 (ArchiMate Library)

If you upgrade from ADOIT 14.0 to ADOIT 15.1, you do not have to create a new database and import a migration package if you are using the ArchiMate Library.

note

This approach is also valid if you are using an ArchiMate Library with changes in the metamodel.

If you are using ADOIT 14.0 with the ADOIT Standard Application Library or another specific library, read on here.

Prerequisites

  • You will need the installation package for a successful and complete migration.
  • Before you start the migration, we strongly recommend creating a backup of the database.

Migration

The migration consists of the following steps:

  1. Stop the ADOIT 14.0 application server and the Apache Tomcat web server.

  2. Export the library-specific component settings.

  3. Back up comments and deployment-specific configuration settings.

  4. Install ADOIT 15.1 according to the ADOIT 15.1 Installation Manual:

    a. Install the rich client for use as an application server and for using the Administration Toolkit.

    b. Install the web client to host ADOIT 15.1 as a web application.

  5. Start the ADOIT 15.1 Administration Toolkit and log in to the ADOIT database.

  6. Update the application library:

    • If you are using the ArchiMate Library: Databases created with ADOIT 14.0 can still be used with ADOIT 15.1. However, you will not have access to improvements in the ArchiMate Library. (Optionally) Update the library in the ADOIT database. A new version of the ArchiMate Library can be found in the folder "04 Sample Data\Library" in the installation package.

    • If you are using an ArchiMate Library with changes in the metamodel: Databases created with ADOIT 14.0 can still be used with ADOIT 15.1. However, you will not have access to improvements in the ArchiMate Library. (Optionally) Contact your ADOIT consultant to upgrade your application library.

  7. Import the library-specific component settings if you updated the application library.

  8. Migrate comments and deployment-specific configuration settings.

  9. In the ADOIT 15.1 Administration Toolkit, execute the script 15.0 - repo 1.js (menu Settings - Execute JavaScript file). The respective file can be found in the folder "05 Migration" on the installation medium. For details on this script, see Executing the Script "15.0 - repo 1.js".

  10. Start the ADOIT 15.1 application server and the Apache Tomcat web server. If ADOIT 15.1 is working properly, you can uninstall ADOIT 14.0.

note

After the migration, users will have the same system roles (and user groups) as before. (Optionally) You can transfer the users to the new standard system roles User, Reader and MM and Integration Administrator. For details, see Transfer Users to the New Standard System Roles.

note

For further information and details on the above steps, please refer to the Installation Manual and to the sections "Make a Manual Backup" , "Restore a Manual Backup" and "Update Library" in the Administration Manual.

Migration from ADOIT 11.0/11.1/12.0/12.1/13.0 to ADOIT 15.1 (ArchiMate Library)

A migration from ADOIT 11.0/11.1/12.0/12.1/13.0 to ADOIT 15.1 without further assistance by BOC is possible if you are using the ArchiMate Library. You will have to create a new database and import a migration package.

note

This approach is also valid if you are using an ArchiMate Library with changes in the metamodel. You will need a new version of your library. Please contact your ADOIT consultant to upgrade your library.

If you are using ADOIT 11.0/11.1/12.0/12.1/13.0 with the ADOIT Standard Application Library or another specific library, read on here.

Prerequisites

  • You will need the installation package for a successful and complete migration.

Migration

The migration consists of the following steps:

  1. Stop the ADOIT 11.0/11.1/12.0/12.1/13.0 application server and the Apache Tomcat web server.

  2. Export the library-specific component settings and a migration package.

  3. Back up comments and deployment-specific configuration settings.

  4. Install ADOIT 15.0 according to the ADOIT 15.1 Installation Manual:

    a. Install the rich client for use as an application server and for using the Administration Toolkit.

    b. Install the web client to host ADOIT 15.1 as a web application.

  5. Create a database:

    • If you are using the ArchiMate Library: A new version of the ArchiMate Library can be found in the folder "04 Sample Data\Library" in the installation package. Initialize the new ADOIT database with this library file.

    • If you are using an ArchiMate Library with changes in the metamodel: Please contact your ADOIT consultant to upgrade your application library. Initialize the new ADOIT database with the new library file you have received from your ADOIT consultant.

  6. Start the ADOIT 15.1 Administration Toolkit and log in to the new database.

  7. Import the migration package and the library-specific component settings.

  8. Migrate comments and deployment-specific configuration settings.

  9. In the ADOIT 15.1 Administration Toolkit, execute the script 15.0 - repo 1.js (menu Settings - Execute JavaScript file). The respective file can be found in the folder "05 Migration" on the installation medium. For details on this script, see Executing the Script "15.0 - repo 1.js".

  10. Start the ADOIT 15.1 application server and the Apache Tomcat web server. If ADOIT 15.0 is working properly, you can uninstall ADOIT 11.0/11.1/12.0/12.1/13.0.

note

After the migration, users will have the same system roles (and user groups) as before. (Optionally) You can transfer the users to the new standard system roles User, Reader and MM and Integration Administrator. For details, see Transfer Users to the New Standard System Roles.

note

For further information and details on the above steps, please refer to the Installation Manual and to the sections "Make a Manual Backup" and "Restore a Manual Backup" in the Administration Manual.

Migration from ADOIT 14.0/15.0 to ADOIT 15.1 (Standard Library)

If you upgrade from ADOIT 14.0/15.0 to ADOIT 15.1, you do not have to create a new database and import a migration package if you are using the ADOIT Standard Application Library.

note

This approach is also valid if you are using an ADOIT Standard Application Library with changes in the metamodel or functional extensions or another specific library.

If you are using ADOIT 14.0/15.0 with the ArchiMate Application Library, read on here (for ADOIT 14.0) or here here (for ADOIT 15.0).

Prerequisites

  • You will need the installation package for a successful and complete migration.

Migration

The migration consists of the following steps:

  1. Stop the ADOIT 14.0/15.0 application server and the Apache Tomcat web server.

  2. Back up comments and deployment-specific configuration settings.

  3. Install ADOIT 15.1 according to the ADOIT 15.1 Installation Manual:

    a. Install the rich client for use as an application server and for using the Administration Toolkit.

    b. Install the web client to host ADOIT 15.1 as a web application.

  4. Migrate comments and deployment-specific configuration settings.

  5. Start the ADOIT 15.1 application server and the Apache Tomcat web server. If ADOIT 15.1 is working properly, you can uninstall ADOIT 14.0/15.0.

note

For further information and details on the above steps, please refer to the Installation Manual and to the sections "Make a Manual Backup" and "Restore a Manual Backup" in the Administration Manual.

Migration from ADOIT 11.0/11.1/12.0/12.1/13.0 to ADOIT 15.1 (Standard Library)

A migration from ADOIT 11.0/11.1/12.0/12.1/13.0 to ADOIT 15.1 without further assistance by BOC is possible if you are using the ADOIT Standard Application Library. You will have to create a new database and import a migration package.

note

This approach is also valid if you are using an ADOIT Standard Application Library with changes in the metamodel or functional extensions or another specific library. You will need a new version of your library. Please contact your ADOIT consultant to upgrade your library.

If you are using ADOIT 11.0/11.1/12.0/12.1/13.0 with the ArchiMate Application Library, read on here.

Prerequisites

  • You will need the installation package for a successful and complete migration.

Migration

The migration consists of the following steps:

  1. Stop the ADOIT 11.0/11.1/12.0/12.1/13.0 application server and the Apache Tomcat web server.

  2. Export the library-specific component settings and a migration package.

  3. Back up comments and deployment-specific configuration settings.

  4. Install ADOIT 15.1 according to the ADOIT 15.0 Installation Manual:

    a. Install the rich client for use as an application server and for using the Administration Toolkit.

    b. Install the web client to host ADOIT 15.1 as a web application.

  5. Create a database:

    • If you are using the ADOIT Standard Application Library: A new version of the ADOIT Standard Application Library can be found in the folder "04 Sample Data\Library" in the installation package. Initialize the new ADOIT database with this library file.

    • If you are using an ADOIT Standard Application Library with changes in the metamodel or functional extensions or another specific library: Please contact your ADOIT consultant to upgrade your application library. Initialize the new ADOIT database with the new library file you have received from your ADOIT consultant.

  6. Start the ADOIT 15.1 Administration Toolkit and log in to the new database.

  7. Import the migration package and the library-specific component settings.

  8. Migrate comments and deployment-specific configuration settings.

  9. Start the ADOIT 15.1 application server and the Apache Tomcat web server. If ADOIT 15.1 is working properly, you can uninstall ADOIT 11.0/11.1/12.0/12.1/13.0.

note

For further information and details on the above steps, please refer to the Installation Manual and to the sections "Make a Manual Backup" and "Restore a Manual Backup" in the Administration Manual.

Migration from All Other Versions to ADOIT 15.1

If you are using ADOIT 10.0/10.1 or earlier versions, the migration to ADOIT 15.1 requires support by BOC.

note

For details on the necessary steps to migrate your version of ADOIT to ADOIT 15.1, please contact your ADOIT consultant.

Switch to ArchiMate Library

If you are using ADOIT 15.0 or earlier versions, and want to switch to using the ArchiMate Application Library, the migration to ADOIT 15.1 requires support by BOC.

note

For details on the necessary steps to migrate your version of ADOIT to ADOIT 15.1, please contact your ADOIT consultant.

How to Install a Hotfix for ADOIT 15.1

Hotfixes resolve software errors and security issues. Please note that the most current hotfix always includes the modifications of previous hotfixes. Only the latest hotfix has to be installed to get all fixes.

If you install a hotfix for ADOIT 15.1, you do not have to create a new database and import a migration package.

Downloading a Hotfix

  • In the majority of cases, you are notified of hotfixes by your ADOIT consultant.

  • The version format of a hotfix is 15.1.x (for example: 15.1.1 or 15.1.2).

  • Download the hotfix from the BOC website (your ADOIT consultant will email you a link).

  • The installation utilizes a full, standalone release package.

Installing a Hotfix

Installing a hotfix consists of the following steps:

  1. Stop the ADOIT 15.1 application server and the Apache Tomcat web server.

  2. Backup comments and deployment-specific configuration settings.

  3. Install ADOIT 15.1.x according to the ADOIT 15.1 Installation Manual:

    a. Install the rich client for use as an application server and for using the Administration Toolkit.

    b. Install the web client to host ADOIT 15.1.x as a web application.

  4. Migrate comments and deployment-specific configuration settings.

  5. Start the ADOIT 15.1.x application server and the Apache Tomcat web server. If ADOIT 15.1.x is working properly, you can uninstall ADOIT 15.1.

note

For further information and details on the above steps, please refer to the Installation Manual and to the sections "Make a Manual Backup" and "Restore a Manual Backup" in the Administration Manual.

Update Scripts

Executing the Script "15.0 - repo 1.js"

This script updates the repository. The following changes are made:

  • Note icon Note

Enables the option Use legacy formatting options for all Note icon Notes that have been migrated to ADOIT 15.0. This will ensure that all models containing Note icon Notes will look as they did before.

note

Newly created Note icon Notes use the new and improved formatting options in ADOIT 15.0 (see Formatted Annotations in Models). To also use the improved formatting options for migrated Note icon Notes, Use legacy formatting options needs to be turned off (in the Notebook chapter "General" in the group "Legacy formatting options").

Transfer Users to the New Standard System Roles

If you migrate from an earlier version of ADOIT to ADOIT 15.1, you can transfer the users to the new standard system roles User, Reader and MM and Integration Administrator. You will need to execute three scripts in the Administration Toolkit.

What Has Changed?

Default system roles

  • The Enterprise Architect and Contributor system roles have been replaced by the new User system role. Members of this system role have access to the "Design & Document" and "Control & Release" scenarios. For users who model the EA infrastructure in ADOIT.
  • The Reader system role is new. Members of this system role have access to the "Read & Explore" scenario. For users who want to view architecture artefacts in ADOIT.
  • The MM and Integration Administrator system role is also new. Members of this system role can choose between various predefined metamodel profiles in the web client. For power users that should have control over the modelling method.
  • The Application Owner system role has been removed. It served as a template for assigning user rights for the available metamodel elements (= metamodel rights).

The default user groups that you can optionally import have also been updated:

  • Enterprise Architect -> User
  • Contributor -> Reader
  • Reader -> Organisation Portal Reader

Prerequisites

  • You are using using the ArchiMate Library.
  • The migration to ADOIT 15.1 has been successfully completed.
  • Before you start, we strongly recommend creating a backup of the database.

Procedure

  • In the ADOIT 15.1 Administration Toolkit, execute the following scripts in the listed order (menu Settings - Execute JavaScript file):
    • 15.0 - repo 2 (role migration).js
    • 15.0 - repo 3 (cmp settings role migration).js
    • 15.0 - repo 4 (old role removal).js

These scripts can be found in the folder "05 Migration" on the installation medium. How the scripts work is described in the sections below.

15.0 - repo 2 (role migration).js

This script changes the role assignment of users. It makes sure that users are transferred to the new standard system roles:

Transfer to new system roles

  • Users with the Enterprise Architect system role will have the new User and MM and Integration Administrator system roles assigned.
  • Users with the Contributor system role will have the new User system role assigned.
  • After successful completion, the assignment to the old Enterprise Architect and Contributor system roles will be removed.

15.0 - repo 3 (cmp settings role migration).js

This script changes the role assignment to component settings. It makes sure that users can access the same functionalities in the ADOIT web client as they could before:

  • If the following component settings have the Enterprise Architect and/or Contributor system roles assigned, the new system role User will be assigned:

    Change of role assignment to component settings

    • Authentication (role assignment in user mapping)

    • Property Filter

    • Reporting Board

    • Validation

    • Web Modules (with three exceptions, see below)

  • If the following component settings have the Enterprise Architect and/or Contributor system roles assigned, the new system role MM and Integration Administrator will be assigned:

    Change of role assignment to component settings

    • Web Module "Generic Connector" (and other Integration Framework connectors, if available)
    • Web Module "Metamodel Profiles"
    • Web Module "Management Office Integration (MOI)"
  • After successful completion, the assignment to the old Enterprise Architect and Contributor system roles will be removed.

15.0 - repo 4 (old role removal).js

After the preceding migration scripts have been executed, this script permanently removes the Enterprise Architect and Contributor system roles as they are no longer needed.

System roles removal