Skip to main content
Version: 13.0

After the Installation

The following shortcuts will show up on the start menu entry of ADOIT 13.0 (after a complete installation):

  • Manuals

    The ADOIT user documentation in English and German.

  • Administration Toolkit

    Used by a ADOIT-Administrator for example to create users or assign rights among other tasks.

  • Create a new database

    A tool used to create new ADOIT databases.

Now you should proceed with the following steps:

Create Database#

After the installation of ADOIT, a database has to be created (see "Create Database").

Import Sample Users#

Are you using the ADOIT Standard Application Library or the ArchiMate Application Library? Then import the sample users in the Administration Toolkit now. The sample users contain the default user groups and the default system roles. This configuration will allow your users to access the different application scenarios of ADOIT as well as the Organisation Portal and the EA workflow.

  1. Start the Administration Toolkit with the default user "Admin" (password: "password") and the name of the previously installed ADOIT 13.0 database.

  2. Import the sample users into the ADOIT database (User Management - Import users). The respective file can be found in the folder “04 Sample Data/Users“ on the installation medium. When importing the sample users you have to activate the following options:

    • Recursive

    • Including system roles

    • Including metamodel rights

    • Assign current repository automatically

  3. Create a user in the Administration Toolkit for every person who wants to work with ADOIT (User Management - Create user).

  4. Add the users to the appropriate user groups and system roles depending on their tasks in ADOIT. The sample users can serve as a template for this.

note

You can import the ADOIT Standard Migration Package instead of the sample users. This package contains the sample users and example models. The example models serve to illustrate the graphical gathering of your enterprise architecture with ADOIT. The respective file can be found in the folder “04 Sample Data/Migration Package“ on the installation medium.

Default User Groups#

The following user groups comprise the default user groups:

  • Enterprise Architect

    Members of the user group "Enterprise Architect" will have write access to the standard model group and the standard object group. Enterprise architects administer the EAM infrastructure. They assign Applications and other objects to Contributors.

  • Contributor

    Members of the user group "Contributor" will only have read access to the standard model group and the standard object group (with the exception of the Applications and other objects for which they are assigned as responsible).

  • Reader

    Typically this user group will only hold one technical user account. This user account is used when users access the Organisation Portal via the link on the web client login page.

  • Default group

    Typically this user group will only hold technical user accounts. These user accounts are used when synchronizing objects between ADOIT and another BOC Management Office product and in other special scenarios.

Default System Roles#

The following system roles comprise the default system roles:

EA Workflow

  • Contributor

    Contributors submit objects to review. They can also create new versions of already released objects in order to adapt them.

  • Architect

    Architects can execute all transitions. Unlike Contributors, they can also release or reject objects.

  • Administrators

    Administrators can also execute all transitions, but they do not receive automatic notifications.

note

EA workflow roles are only available if the EA workflow is enabled.

Metamodel Rights

  • Application Owner

    This system role serves as a template for assigning user rights for the available metamodel elements (= metamodel rights). Application owners may, for example, create Applications, but no Goals.

Application Scenarios (ArchiMate Application Library)

  • Enterprise Architect

    Members of the system role Enterprise Architect will have access to the "Design & Document" and "Control & Release" scenarios. Via the "Design & Document" scenario users will be able to design services and architectures and to plan initiatives. The purpose of the "Control & Release" scenario is to let users review and release objects with a single click.

  • Contributor

    Members of the system role Contributor have access to the scenario "Explore & Contribute". Based on the permissions assigned at the user group level, usually they cannot create objects and models. Via the "Explore & Contribute" scenario users can get a quick overview of architecture artefacts in ADOIT and contribute to the gathering of enterprise architecture information.

Application Scenarios (ADOIT Standard Application Library)

  • Enterprise Architect

    Members of the system role Enterprise Architect will have access to all scenarios. Via the "Design & Document" scenario users will be able to design services and architectures and to plan initiatives. The purpose of the "Control & Release" scenario is to let users review and release objects with a single click. The purpose of the "Govern & Manage" scenario is to let users get the big picture of your enterprise.

  • Contributor

    Members of the system role Contributor have access to the scenarios "Design & Document" and "Control & Release". Based on the permissions assigned at the user group level, usually they cannot create objects and models.

Organisation Portal

  • Organisation Portal

    Typically only one technical user account will have this system role. This user account is used when users access the Organisation Portal via the link on the web client login page.

Install Web Client#

In order to host ADOIT as a web application, the web client has to be installed and configured next (see "Install Web Client").