New Features in ADOIT 16.0

ADOIT 16.0 is out! With the novel concept of workspaces as well as the first template Application Investment Planning, we are raising the bar for collaboration in ADOIT. What else does the new major release bring? Just read on to find out which new features and improvements are included in ADOIT 16.0.

New Features for All Users

Workspaces

Workspaces complement the application scenarios of ADOIT such as "Design & Document" or "Read & Explore".

A Tool for Decision Making

Workspaces bundle together multiple functionalities to provide a guided approach to solving specific business needs. They empower the user to perform relevant tasks and make decisions using resources such as dedicated visualisations, modeling environments tailored to specific use cases, and machine learning capabilities.

Collaboration

Workspaces serve as collaboration hubs for enterprise architecture. Teams can work together on specific tasks - even at the same time! Invite your colleagues and delegate tasks directly to them. The barriers to collaboration are low: Simple interaction options such as surveys or input forms help colleagues with less ADOIT experience to contribute their expertise.

Templates

A workspace is created based on a template. In ADOIT 16.0, the following template is available (with more coming soon):

• Application Investment Planning

Read on to find out more about this template!

Application Investment Planning

Open a new chapter in planning the investment strategy for your application portfolio with ADOIT 16.0 - at no extra charge for existing customers and for all users!

The new Application Investment Planning template is a collaborative approach to assessing the fitness of your applications and defining their investment strategy.

Here's how it works:

• First, create a new workspace and add the users you want to collaborate with.

• Next, you and your team need to select a set of applications for assessment.

• Assessment of the applications is done by answering surveys.

note

You can fill out the surveys on your own or forward them to subject matter experts from business and IT. Your colleagues can then access the survey directly from the mailbox with one click, without having to navigate through the application beforehand. This makes these surveys particularly suitable for ADOIT beginners who are not as familiar with the use of ADOIT as the EA experts in your company.

• Based on the evaluation, the applications are then placed in a TIME model. Gartner's TIME model proposes four investment strategies (Tolerate, Invest, Migrate and Eliminate).

• Once you have gathered all of the necessary information, you can make a final decision on the investment strategy for each application:

  • You can confirm the calculated investment strategy.

  • Or you can opt for the investment strategy determined by a machine learning algorithm based on previous decisions for similarly rated applications.

  • Alternatively, you can simply choose the investment strategy yourself.

• When you are finished, you have access to a summary that provides an overview of the status of all applications in the workspace.

We hope that you and your colleagues will enjoy the new Application Investment Planning service and that it will make your work easier. In the future, we plan to introduce other services, including Strategic Roadmapping for defining requirements and Architecture Risk Assessment for uncovering vulnerabilities in your EA architecture.

note

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

New Features for ADOIT Administrators

Control Access to Application Investment Planning Template

As an ADOIT administrator, you can grant or deny access to the Application Investment Planning template. Assign the following web modules to the appropriate system roles:

• Workspaces

• Template: Application Investment Planning

note

For details on how to assign web modules, please refer to the section "Assign Web Modules" in the Administration Manual.

Import Users from Excel

ADOIT 16.0 provides new tools for managing users accounts. On the Admin Page, you can download a template Excel file that contains columns for the information required to create a new user. You can capture users with this template, and then import users in bulk.

note

For details, please refer to the section "Import Users from Excel" in the Administration Manual.

ADOIT Now Supports PostgreSQL

As an alternative to SQL Server and Oracle, ADOIT now supports the powerful open source database system PostgreSQL. ADOIT is compatible with PostgreSQL 12.2 or higher.

You can create the database automatically using the tool Database Administration (adbinstws.exe) or create the database manually using pgAdmin or create the database from script.

note

You can find a guide on how to create a PostgreSQL database for ADOIT in the online help (see "Creating a PostgreSQL Database").

Removed Features

This section lists features that have been removed from ADOIT 16.0.

ADOIT Standard Application Library Discontinued

With ADOIT 16.0, we are finally retiring the ADOIT Standard Application Library, the BOC-specific proprietary application library based on international standards.

ADOIT 8.5 (in 2018) introduced the ArchiMate Application Library, with the goal of eventually replacing the ADOIT Standard Application Library. The ArchiMate Application Library was expanded to include the tried-and-true attribute set from the ADOIT Standard Application Library to facilitate this. Now the time has come and for the first time we are no longer shipping both libraries in parallel.

note

Are you using ADOIT 15.1 or earlier versions with the ADOIT Standard Application Library? Your ADOIT account manager will be happy to help you migrate to ADOIT 16.0.

Migration from an Earlier Version of ADOIT to ADOIT 16.0

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/15.1 to ADOIT 16.0 (ArchiMate Library)

If you upgrade from ADOIT 15.0/15.1 to ADOIT 16.0, 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/15.1 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/15.1 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 16.0 according to the ADOIT 16.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 16.0 as a web application.

5. Start the ADOIT 16.0 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/15.1 can still be used with ADOIT 16.0. 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/15.1 can still be used with ADOIT 16.0. 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 16.0 application server and the Apache Tomcat web server. If ADOIT 16.0 is working properly, you can uninstall ADOIT 15.0/15.1.

note

(Optionally) In case it did not already happen as part of the upgrade to ADOIT 15.0/15.1, 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 16.0 (ArchiMate Library)

If you upgrade from ADOIT 14.0 to ADOIT 16.0, 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 16.0 according to the ADOIT 16.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 16.0 as a web application.

5. Start the ADOIT 16.0 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 16.0. 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 16.0. 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 16.0 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 16.0 application server and the Apache Tomcat web server. If ADOIT 16.0 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 14.0/15.0/15.1 to ADOIT 16.0 (Standard Library)

If you upgrade from ADOIT 14.0/15.0/15.1 to ADOIT 16.0, 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/15.1 with the ArchiMate Application Library, read on here (for ADOIT 14.0) or here here (for ADOIT 15.0/15.1).

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/15.1 application server and the Apache Tomcat web server.

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

3. Install ADOIT 16.0 according to the ADOIT 16.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 16.0 as a web application.

4. Migrate comments and deployment-specific configuration settings.

5. Start the ADOIT 16.0 application server and the Apache Tomcat web server. If ADOIT 16.0 is working properly, you can uninstall ADOIT 14.0/15.0/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.

Migration from All Other Versions to ADOIT 16.0

If you are using ADOIT 13.0 or earlier versions, the migration to ADOIT 16.0 requires support by BOC.

note

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

Switch to ArchiMate Library

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

note

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

How to Install a Hotfix for ADOIT 16.0

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 16.0, 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 16.0.x (for example: 16.0.1 or 16.0.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 16.0 application server and the Apache Tomcat web server.

2. Backup comments and deployment-specific configuration settings.

3. Install ADOIT 16.0.x according to the ADOIT 16.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 16.0.x as a web application.

4. Migrate comments and deployment-specific configuration settings.

5. Start the ADOIT 16.0.x application server and the Apache Tomcat web server. If ADOIT 16.0.x is working properly, you can uninstall ADOIT 16.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.

Update Scripts

Executing the Script "15.0 - repo 1.js"

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

• Note

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

note

Newly created Notes use the new and improved formatting options in ADOIT 15.0 or higher. To also use the improved formatting options for migrated 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.0 or higher, 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?

• 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.0 or higher has been successfully completed.
• Before you start, we strongly recommend creating a backup of the database.

Procedure

• In the ADOIT 15.0 or higher 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:

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

  

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

  

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