Upgrade from ADOIT 14.0 to ADOIT 16.0 (ArchiMate Library)
If you are planning to upgrade from ADOIT 14.0 to ADOIT 16.0, and you're using the ArchiMate Application Library, this guide will walk you through the necessary steps to ensure a smooth transition.
If you are using ADOIT 14.0 with the ADOIT Standard Application Library or another specific library, read on here.
Prerequisites
Before you proceed, note the following prerequisites:
Before installing, make sure that all Hardware/Software Requirements are met.
Download the ADOIT 16.0 installation package (your ADOIT consultant will email you a link).
Create a backup of the ADOIT database.
ArchiMate Application Library for ADOIT 16.0
You can get started right away if you are using the default ArchiMate Application Library that comes with ADOIT.
Please contact your ADOIT consultant if you are using an ArchiMate Application Library with changes in the metamodel to upgrade your application library.
Stop Services
First, the ADOIT 14.0 application server and the Apache Tomcat web server have to be stopped.
To stop the services (on Windows):
Open Services. Press <Windows> + <R> to open the Run box, enter services.msc, and then click OK.
Stop the ADOIT application server (service name e.g. "ADOITServer14.0Service") and the Apache Tomcat web server (service name e.g. "Tomcat9").
Export Component Settings
Component settings allow you to adapt a wide range of library-specific features. To ensure you don't lose your settings during the upgrade, it's essential to export the ADOIT 14.0 component settings now. Later, you will have to re-import them after updating the application library.
To export the component settings:
In the ADOIT 14.0 Administration Toolkit, go to Library Management > Component Settings.
Select your library, and then click Export component settings.
Select Export all component settings to export all settings at once. Alternatively, you can clear the check box and select the component settings you want to export.
In the Export file box, enter a name for the export file.
Click Export. The data is exported.
Backup Deployment-Specific Data
Deployment-specific data encompasses various settings and information that are not stored in the database. This includes comments on models and objects, settings such as server ports, and more.
Depending on your ADOIT 14.0 installation, you have to back up the following folders and files:
ADOIT Application Server Configuration
<ADOIT 14.0 application server>/conf/server.conf
(contains the database name, application server or aworker processes ports, and trusted IP address of the web server).<ADOIT 14.0 application server>/conf/adoxx.conf
(optional, if parameters have been changed from their default value)<ADOIT 14.0 application server>/conf/adoxx_web_conf.js
(optional, if parameters have been changed from their default value)
Apache Tomcat Configuration
<Tomcat>/webapps/ADOIT14_0/adoxx_web.properties
(contains the application server IP address and definition of aworker processes)<Tomcat>/webapps/ADOIT14_0/WEB-INF/classes/logback.xml
(optional, if logging parameters have been changed)<Tomcat>/webapps/ADOIT14_0/WEB-INF/web.xml
(optional, if additional file types have been whitelisted for uploading)<Tomcat>/webapps/ADOIT14_0/WEB-INF/registry/rest/RESTAuthorization.xml
(part of the REST API configuration)
Comment Data
<Tomcat>/webapps/ADOIT14_0/WEB-INF/registry/collaboration
(contains XML files that hold all comments for a model or object)<Tomcat>/webapps/ADOIT14_0/WEB-INF/registry/upload
(contains files that were uploaded along with comments)<Tomcat>/webapps/ADOIT14_0/WEB-INF/registry/axw.ids
(contains the last assigned and highest comment ID)
Install and Configure ADOIT 16.0 Rich Client
Now, it's time to install and configure the ADOIT 16.0 rich client, which serves as an application server and is required for using the Administration Toolkit. Detailed instructions are provided in the following sections.
Perform Installation
Install the ADOIT 16.0 rich client now. Depending on your deployment scenario, you must perform the following steps:
Install ADOIT as an application server on the designated server machine.
Install ADOIT for using the Administration Toolkit, for example on client machines or on a terminal server.
To perform the installation:
- Double-click
setup.exe
located in the02 Rich Client
folder within the ADOIT 16.0 installation package, and then follow the instructions provided by the setup wizard.
For detailed instructions on the installation process, see Install Rich Client.
Configure Application Server
After the installation is complete, configure the ADOIT 16.0 application server. Unlike a new installation where you'd set initial values, you will use your backup ADOIT 14.0 application server configuration files and transfer the values from there.
To configure the application server:
Navigate to the directory
<ADOIT 16.0 application server>/conf
.Edit the configuration file
server.conf
and transfer the values from your backup file, including the database name, application server or aworker processes ports, and the trusted IP address of the web server.Optional: Edit the configuration files
adoxx.conf
andadoxx_web_conf.js
, and transfer the values from your backup files if parameters in these files were changed in ADOIT 14.0.
Example
For example, if you previously modified the file adoxx_web_conf.js
to set the standard language
the web client should be started with, then copy the value of the parameter
ADOXX_WEB_CLIENT_LANGUAGE
to the new adoxx_web_conf.js
file.
Always merge your changes into the new configuration files - never overwrite them!
Update Application Library
Next, your application library needs to be updated.
How Does This Affect My Library?
If you are using the default ArchiMate Application 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 Application Library. Optional: Update the library in the ADOIT database. A new version of the ArchiMate Application Library can be found in the folder
04 Sample Data\Library
in the installation package.If you are using an ArchiMate Application 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 ArchiMate Application Library. Optional: Contact your ADOIT consultant to upgrade your application library.
Perform Update
To upgrade your application library:
Start the ADOIT 16.0 Administration Toolkit and log in to the ADOIT database.
Go to Library Management, select your library, and then click Update library.
Click Search... and select the file you want to import.
Clear the Do not import component settings check box.
RemarqueIf Do not import component settings is disabled, your existing component settings will be overwritten with those from the import file. This is necessary for adding new component settings not present in ADOIT 14.0. Later, you will re-import your exported component settings to restore your previous settings for all component settings that were already present in ADOIT 14.0.
Click Import. The library is updated.
Import Component Settings
If you've updated the application library in the previous step, it's time to re-import your exported component settings.
To import the component settings:
In the ADOIT 16.0 Administration Toolkit, go to Library Management > Component Settings.
Select your library, and then click Import component settings.
Click Search... and select the file you want to import. Then, click Import.
Click All to select all component settings for import, and then click OK. When prompted to continue, click Yes. The data is imported.
Execute Migration Scripts
If you're using the ArchiMate Application Library, and updated it, it's essential to execute
migration scripts at this point. You can find these scripts in the ADOIT 16.0 installation package
under 05 Migration
.
The ArchiMate Application Library has evolved from ADOIT 14.0 to ADOIT 16.0, incorporating methodical improvements. To prevent potential data loss, you need to adjust your repository content to fit the new method, and this is where the migration scripts come into play.
To execute the migration scripts:
In the ADOIT 16.0 Administration Toolkit, go to Settings > Execute JavaScript file.
Click Search... and select the file
15.0 - repo 1.js
. Then, click Execute.Repeat steps 1 - 2 for the script
15.1 - repo grouping_layer.js
.
For details on the scripts, see Migration Scripts.
Install Application Server as a Service
With the rich client installation and configuration tasks completed, it's now time to install the ADOIT 16.0 application server as a service.
Open the Windows Command Prompt as an administrator. Press <Windows> + < R> to open the Run box, enter cmd, and then press <Ctrl> + <Shift> + <Enter>.
Navigate to the directory
<ADOIT 16.0 application server>
.Type
aserver.exe -i
to install the Windows Service (e.g. ADOITServer16.0Service).
The application server is now installed as a service. Do not start the service yet.
Install and Configure ADOIT 16.0 Web Client
Now, you need to deploy the ADOIT 16.0 web client and configure it using backup files from your ADOIT 14.0 deployment. You'll benefit from reduced configuration efforts by utilising the same Tomcat instance that already hosts the ADOIT 14.0 web client. Detailed instructions are provided in the following sections.
Deploy Web Client
Deploy the ADOIT 16.0 web application to Apache Tomcat now by copying the necessary files:
- Copy the file
ADOIT16_0.war
to the directory<Tomcat>/webapps
. This file can be found in the folder03 Web Client
within the ADOIT 16.0 installation package.
The ADOIT 16.0 web client is now deployed. Do not start the Apache Tomcat service yet.
Configure Web Client
Now, it's time to configure the ADOIT 16.0 web client. Unlike a new installation where you'd set initial values, you will use your backup ADOIT 14.0 Apache Tomcat configuration files and transfer the values from there. You will also import the comment data.
To configure the web client:
Navigate to the directory
<Tomcat>/webapps
.Open the file
ADOIT16_0.war
with a file archiver and perform the following steps on its contents:Edit the configuration file
adoxx_web.properties
. Transfer the values from your backup file, including the application server IP address and definition of aworker processes.Optional: Edit the configuration files
WEB-INF/classes/logback.xml
,WEB-INF/web.xml
andWEB-INF/registry/rest/RESTAuthorization.xml
, and transfer the values from your backup files if parameters in these files were changed in ADOIT 14.0.Copy the backup folders
collaboration
andupload
, as well as the backup fileaxw.ids
, to the folderWEB-INF/registry
.
Save the changes.
Always merge your changes into the new configuration files - never overwrite them!
Uninstall ADOIT 14.0
You've completed the ADOIT 16.0 installation; now, it's time to uninstall ADOIT 14.0.
Uninstall the ADOIT 14.0 application server, and any other ADOIT 14.0 rich client installations for using the Administration Toolkit. You can do this through the control panel.
Remove the ADOIT 14.0 web application from Apache Tomcat.
For detailed instructions on how to uninstall, see Uninstall ADOIT.
Start Services
Finally, the ADOIT 16.0 application server and the Apache Tomcat web server have to be started.
To start the services (on Windows):
Open Services. Press <Windows> + <R> to open the Run box, enter services.msc, and then click OK.
Start the ADOIT application server (service name e.g. "ADOITServer16.0Service") and the Apache Tomcat web server (service name e.g. "Tomcat9").
You can access the web client via the following address:
http://<SERVER_NAME>:<TOMCAT_PORT>/ADOIT16_0/
. Here, <SERVER_NAME>
represents the server
machine's name, and <TOMCAT_PORT>
corresponds to the HTTP/1.1 Connector Port that was configured
during setup (the default value is “8000”).
After the migration, users will have the same system roles (and user groups) as before. Optional: If you're using the ArchiMate Application Library, 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.