Accéder au contenu principal
Version: 21.0

Tools

The Tools menu provide access to two types of settings:

General​

The following settings are available in this section:

Support​

The following settings are available in this section:

  • Information: Downloading a support information package (SIP) containing logging and system information.

  • Debug Mode: Managing debug mode.

  • Maintenance: Managing maintenance mode and the operations tool.

  • Repository Statistics: View information about your ADOIT deployment.

  • Support Access: Managing access for BOC employees to your ADOIT Administration for troubleshooting and support purposes.

System Preferences​

To access the system preferences:

  • Go to Home > More options, and then click System Preferences.

The System Preferences window opens. It contains the following tabs:

These tabs are discussed in more detail in the following sections.

Security Settings​

The following options are available:

Password Strength Settings​

Here you can customise the password strength settings. The following options are available:

  • Minimal password strength: ADOIT determines the strength of passwords based on their length, complexity, and predictability and assigns them a value of 0 - 100%. Here you can set the minimum strength passwords must have: from very weak (0%), weak (20%), good (40%), strong (60%) to very strong (80%).

  • Custom password rule: By default, a new password must have at least 8 characters and contain at least one digit (e.g. 0-9) and uppercase as well as lowercase characters (e.g. A-Z, a-z). You can change this setting and specify a custom password rule via a regular expression pattern.

    Examples of custom password rules

    Passwords should have at least 5 characters and contain a lowercase character (e.g. a-z). The Custom password rule field should therefore read:

    ^(?=.*[a-z]).{5,}$

    Passwords should have at least 8 characters and contain a digit (e.g. 0-9), a lowercase character (e.g. a-z) and an uppercase character (e.g. A-Z). The Custom password rule field should therefore read:

    ^(?=.*\d)(?=.*[a-z])(?=.*[A-Z]).{8,}$

  • Number of not allowed previous passwords: Specify the number of previous passwords that are stored by ADOIT and must not be reused on password change.

  • Maximum password age (days): Specify the period of time (in days) that a password can be used before ADOIT requires the user to change it.

  • Minimum password age (days): Specify the period of time (in days) that a password must be used before the user can change it.

Remarque

Passwords must meet the minimum password strength settings (e.g., reach 60%) AND match the custom password rule (e.g., contain at least 8 characters and contain numeric and uppercase and lowercase characters).

Login Settings​

Here you can customise security relevant login settings. The following options are available:

  • Number of allowed login failures: Choose a maximal number of allowed login failures before a user is disabled and cannot log in anymore.

System Preferences – Audit Log​

Please refer to the section Enable Audit Log for details.

File Management​

This tool allows managing auxiliary files (graphic files, scripts…) in the database. To open the file manager:

  • Go to Home > More options, and then click File Management.

The Database File Management window opens. The following functions are available:

  • Search: Search for a file or folder in the database.

  • File and Folder Management: Create new folders, cut and paste files, rename files and folders, delete files and folders, refresh the content of the catalogue.

  • Export: Export files and folders from the database into the file system.

  • Import: Import external files into the database.

Remarque

Only the super user Admin has full access to all files in the database.

Update Database Statistics​

The contents of the database are subject to permanent change: models and objects are created and deleted, libraries imported and much more. Every action creates new information which - over time - slows down the database access. Therefore, it is advisable to update the catalogue statistics of the database system either after major reorganisations or periodically.

Database catalogue statistics are data about the distribution of table and index values which are consulted by the database system for query optimisation. Up-to-date catalogue statistics lead to more efficient execution plans resulting in considerably shorter system response times and thus speeding up the user's work.

To update the database statistics:

Info

Updating the database statistics can take a while. During the update other users will experience significant slowdowns in the database communication with ADOIT. Therefore, we recommend not updating the database statistics during times of heavy use.

Maintenance Method​

When you update the database statistics, you can select the maintenance method:

  • Default settings: These are the default settings as defined in the configuration.

  • Statistics update: The database catalogue statistics are updated, while the indexes are not defragmented.

  • Defragmentation on leaf level: The indexes are defragmented on leaf level, and the database catalogue statistics are updated.

  • Index rebuild: The complete index is defragmented.

  • Index rebuild (online):: The complete index is defragmented while the index remains online. Not available for PostgreSQL databases.

Topic (Table Group)​

When you update the database statistics, you can select for which database tables the selected maintenance method should be performed:

  • All: Maintenance is performed for all database tables.

  • Migration (all data tables except library definition): Maintenance is performed for all database tables containing ADOIT data which are relevant for migrations.

  • Repository (repository list, groups, models, objects and users, relations): Maintenance is performed for all database tables which contain repository data including the repository list.

  • Models (groups, models, objects and users, relations): Maintenance is performed for all database tables which contain repository data excluding the repository list.

  • Objects (groups, objects and users, relations): Maintenance is performed for all database tables which contain object data.

  • Users (groups, objects and users, rights and system roles; no relations): Maintenance is performed for all database tables which contain user data.

  • Metamodel (library definition): Maintenance is performed for all database tables which contain the metamodel definition.

Analyse Bandwidth​

This function allows you to perform a quick, superficial analysis of the bandwidth and response times between the ADOIT Administration and the database server. To analyse the bandwidth:

  • Go to Home > More options, and then click Analyse Bandwidth.

  • Click Start.

Three files (1KB, 1MB, 10MB) will be generated. Then ADOIT measures how long it takes to

  • upload the files to the database (a temp directory will be created in the database),

  • download the files from the database and

  • delete the files from the database.

When the analysis is completed, you can compare your results with the reference values.

Licence Overview​

This page shows you at a glance the total number of available scenario licences as well as the number of scenario licences currently in use. You can also find out quickly about all active ADOIT users including the time of login and the time of the last action. To open the Licence Overview page:

  • Go to Home > More options, and then click Licence Overview.
Remarque

If you have questions about the different types of licences or the difference between concurrent users and named users, please refer to the sections Product Licences vs. Scenario Licences and Named Users vs. Concurrent Users.

Remarque

You can control whether actual login names are shown in this widget by setting the environment variable ADOXX_WEB_TRACK_LOGINS to "true" or "false" in the deployment configuration of the application server container.

Script Execution​

From time to time it can be advantageous to make small modifications of the ADOIT configuration without having to perform a full product configuration life cycle. The function Script Execution allows wrapping the changes into a JavaScript and applying them online.

To execute a JavaScript:

  • Go to Home > More options, and then click Script Execution.

  • Click Browse and select the script you want to execute. You can also drag a file from your computer to the Drag and drop files here to upload area.

  • Select Execute on server to execute the script on the application server. When this option is disabled, the script is executed in the web browser. If you are unsure which option to select, please contact a BOC employee.

  • Click Execute Script.

Attention

Only import tested JavaScripts which you have received from a BOC employee!

Server​

This page allows you to perform various maintenance tasks. To open the Server page:

  • Go to Home > More options, and then click Server.

The following functionalities are available:

  • Restart Environment: Restart the application server and the web application. All users will be logged out. As soon as the application server is up and running again, and the web application is completely initialised, login is possible again.

  • Restart Web Application: Restart the web application. All ADOIT users will be logged out. As soon as the web application is completely initialised, login is possible again.

  • Re-intialise search index: Reinitialize the search index if you if you are encountering problems with the search function in ADOIT. Depending on the number of models and objects in the database this process may take a few minutes.

  • Start LDAP synchronisation: Start the synchronization of users with an LDAP-compliant directory service according to the configuration specified in the ADOIT Administration. The synchronization is triggered for all configured domains. During the synchronization, a progress bar provides information on the current status. After the synchronization, all newly synchronized users and any error codes are displayed for each domain.

  • Clear LDAP Cache: When synchronization of users with an LDAP-compliant directory service is enabled and the option recursiveNodeLookup is enabled for one or more LDAP properties, ADOIT is caching results to speed up performance. To detect changes in the directory structure, this cache is automatically cleared when the web application is restarted, when you start LDAP synchronization here in the ADOIT Administration, or when a periodic synchronization of users with LDAP is triggered.

    Use this button to clear the LDAP cache if recursiveNodeLookup is enabled, there are changes in the directory structure, and you want to make sure that users that log in to ADOIT for the first time will be assigned correctly to system roles, user groups and repositories.

Information​

This page allows you to download support information packages in different sizes. A support information package contains log files of the application server, log files of the web server including the web application as well as configuration files within an encrypted Zip archive. To open the Information page:

  • Go to Home > More options, and then click Information.

The following sizes are available:

  • Support Package SMALL: Downloads log files from the last 24 hours.

  • Support Package MEDIUM: Downloads log files from the last week.

  • Support Package LARGE: Downloads all log files.

Download Support Information Package when Access to the ADOIT Administration is not possible​

You can still download the support package when the ADOIT Administration cannot be reached in case of an error. In order to do so:

  • Open a web browser and navigate to "http://<SERVER_NAME>:<TOMCAT_PORT>/ADOIT21_0/supportinformation".

<SERVER_NAME> is the name of the server machine, <TOMCAT_PORT> is the port at which Apache Tomcat is accessible (by default this is 8000).

Example

If you are running ADOIT locally, the URL should look like this:

"http://localhost:8000/ADOIT21_0/supportinformation"

You can modify the URL to only download log files from a certain time period. In order to do this, add ?logType=<PARAMETER> to the URL. The following parameters that correspond to the package sizes listed above are available: "small", "medium" and "large".

Example

If you are running ADOIT locally and you want to download log files from the last 24 hours, the URL should look like this:

"http://localhost:8000/ADOIT21_0/supportinformation?logType=small"

Remarque

Please provide these log files when you contact our support team.

Debug Mode​

This page allows you to activate the debug mode. The debug mode influences various details in the behaviour of the application and can be used for error analysis. To open the Debug Mode page:

  • Go to Home > More options, and then click Debug Mode.

The following functionalities are available:

Activate Debug Mode​

To activate the debug mode:

  • Click Activate. Enter a duration and, optionally, a reason. Then, click OK.

The debug mode will automatically deactivate after the selected timespan.

Change Duration​

To change the duration of the debug mode:

  • Click Change duration. Modify the duration as needed. Then, click OK.
Deactivate Debug Mode​

To deactivate the debug mode:

  • Click Deactivate.
Attention

The debug mode should never be permanently enabled! It is recommended to only activate the debug mode on request of a BOC employee.

Maintenance​

The Maintenance page allows you to enable maintenance mode and the operations tool:

  • Maintenance Mode: Maintenance mode eases the planning of maintenance windows.

  • Operations Tool: This web application provides access to important functionality relevant for operations, such as upgrading the product.

Maintenance Mode​

Maintenance mode eases the planning of maintenance windows. When maintenance mode is enabled, no further logins to the web application will be allowed and a corresponding message will be displayed. The ADOIT Administration is excluded from maintenance mode and can still be used.

Activate Maintenance Mode​

To activate maintenance mode:

  • Go to Home > More options, and then click Maintenance.

  • Click Activate Maintenance Mode.

  • Choose further options based on your preference:

    • To log out all regular ADOIT users right now, click Log out all non-admin users.

    • To keep maintenance mode enabled even if the web application or the entire environment are later restarted on the Server page, select Keep maintenance mode active after restart.

  • Click Close.

Deactivate Maintenance Mode​

To deactivate maintenance mode:

  • On the Maintenance page, click Deactivate Maintenance Mode.

Operations Tool​

The Operations Tool is a web application that provides access to important operations for administering ADOIT. It is available when needed and allows you to perform certain operations without direct access to the application server or database server.

Start the Operations Tool​

The Operations Tool can be started in different ways depending on the operation you need to perform:

  • From the ADOIT Administration: Go to Home > More options > Maintenance, and click Activate Operations Tool. The Operations Tool starts in maintenance mode. To stop the Operations Tool, return to the Maintenance page and click Deactivate Operations Tool (restarts the environment).

  • Automatically when the database is not initialized: If you deploy ADOIT with an empty, uninitialized database, or if you use the database user ADOxx with the predefined default password, the Operations Tool starts automatically in initialize empty database mode when the application server starts. Use this mode to encrypt the database credentials and initialize the database.

  • Using an environment variable: To start the Operations Tool, set the ADOXX_OPERATIONS_TOOL_MODE environment variable to initdb or maintenance, and restart the environment. Use initdb to start the Operations Tool for database initialization. Use maintenance to start it in maintenance mode. The latter option can be used, for example, if you need to reset or enable the Admin account and cannot access the ADOIT Administration.

Access the Operations Tool​

To access the Operations Tool, open its URL in a web browser. The Operations Tool uses port 9090 by default. To construct the URL, take the URL where ADONIS is available and replace the web server port with port 9090 (for example, http://localhost:9090/).

Make sure that the Operations Tool port is exposed in the deployment configuration of the application server container. For example, in a Kubernetes deployment, configure the Kubernetes networking accordingly to make the Operations Tool port accessible. For development and testing purposes, you can use port forwarding to access the Operations Tool:

kubectl port-forward service/<your-service-name> 9090:9090

If you configure a different port using the OPERATIONS_SERVER_PORT environment variable, expose the corresponding port in your deployment configuration.

Remarque

Access to the Operations Tool is restricted by the OPERATIONS_IP_RESTRICTIONS environment variable. By default, the tool will refuse all incoming connections unless this variable is explicitly defined.

Environment Variables​

You can configure the following environment variables in the deployment configuration of the application server container:

Environment VariableDescription
ADOXX_OPERATIONS_TOOL_MODEForces the application server container to start the Operations Tool in the specified mode. Possible values are initdb for database initialization and maintenance for maintenance mode.
OPERATIONS_SERVER_PORT(Optional) Specifies the port used by the Operations Tool. The default is 9090.
OPERATIONS_IP_RESTRICTIONSSpecifies which IP addresses can access the Operations Tool. If this variable is not configured, access to the Operations Tool is denied. You can specify individual IPv4 or IPv6 addresses, IPv4 wildcards or subnets, and IPv6 subnets. Use * to allow access from all IP addresses.
OPERATIONS_SERVER_CERT(Optional) Specifies the path to the TLS certificate used by the Operations Tool. Not required if secure connections are handled externally (for example, via a Kubernetes Ingress controller).
OPERATIONS_SERVER_KEY(Optional) Specifies the path to the TLS key used by the Operations Tool. Not required if secure connections are handled externally.
OPERATIONS_MAX_FILE_SIZE_UPLOAD(Optional) Specifies the maximum size of an uploaded file in MB. The default is 5 GB.
OPERATIONS_DOWNLOAD_TTL(Optional) Specifies how long files generated by an operation remain available for download. The default is 12 hours.
ADOXX_DBMS_CREDENTIALSSpecifies the encrypted database credentials used to connect to the ADOIT database.

Maintenance​

The Maintenance mode provides access to the following operations:

These operations use the same database connection parameters.

Encrypt Credentials​

Use Encrypt Credentials to encrypt the credentials of the database user that ADOIT uses to connect to the database. This can either be the database user ADOxx or an individual database user.

Encrypt Database Credentials​

To encrypt the database credentials:

  • In the Operations Tool, click Encrypt Credentials.

  • Enter the database username in Username.

  • Enter the corresponding password in Password and Retype Password.

  • Click Encrypt.

Provide the generated encrypted credentials to the application server through the ADOXX_DBMS_CREDENTIALS environment variable.

Reset Admin Password​

To reset the password of the ADOIT super user Admin, for example if the password has been forgotten:

  1. In the Operations Tool, click Reset Admin Password.

  2. Enter the username of the database user in DB User Name.

  3. Enter the corresponding password in DB User Password.

  4. Enter the new password for the Admin account in New Admin Password and Retype New Admin Password.

  5. Configure the database connection parameters as required.

  6. Click Reset Admin Password.

Enable Admin​

To re-enable the ADOIT superuser Admin if the account has been disabled and you can no longer log in to ADOIT:

  1. In the Operations Tool, click Enable Admin.

  2. Enter the username of the database user in DB User Name.

  3. Enter the corresponding password in DB User Password.

  4. Enter the new password for the Admin account in New Admin Password and Retype New Admin Password.

  5. Configure the database connection parameters as required.

  6. Click Enable Admin.

Import Migration Package/Repository​
Remarque

For regular import operations, use the corresponding functions in the ADOIT Administration: Import Repository, Import Migration Package, or Import Migration Package with Multiple Repositories. Use the Operations Tool for these operations if instructed by a BOC employee or if you need to import very large files.

To import a repository, migration package, or multi-repository migration package into the ADOIT database:

  1. In the Operations Tool, click Import Migration Package/Repository.

  2. Enter the username of an ADOIT administrator in Username.

  3. Enter the corresponding password in Password.

  4. Upload the repository or migration package in Archive File.

  5. If the archive is password-protected, enter its password in Archive File Password.

  6. Select the type of archive in Archive Type:

    • Repository (.axr)

    • Migration Package (.axr)

    • Multi-Repository Migration Package (.axm)

  7. If you selected Repository (.axr) or Migration Package (.axr), configure the following options:

    • Select Import as New repository to import the archive as a new repository. If you select this option, Target Repository ID is not required.

    • If you do not select Import as New repository, enter the ID of the repository into which the archive is to be imported in Target Repository ID.

  8. If you selected Multi-Repository Migration Package (.axm), configure the following options:

    • Select Skip Users to exclude users from the import.

    • Optionally, enter a comma-separated list of repository IDs in Repositories to Import. Leave the field empty to import all repositories contained in the migration package.

  9. Configure the database connection parameters as required.

  10. Click Import.

Export Migration Package/Repository​
Remarque

For regular export operations, use the corresponding functions in the ADOIT Administration: Export Repository, Export Migration Package, or Export Migration Package with Multiple Repositories. Use the Operations Tool for these operations if instructed by a BOC employee or if you need to export very large files.

To export a repository, migration package, or multi-repository migration package:

  1. In the Operations Tool, click Export Migration Package/Repository.

  2. Enter the username of an ADOIT administrator in Username.

  3. Enter the corresponding password in Password.

  4. Select the type of archive in Archive Type:

    • Repository (.axr)

    • Migration Package (.axr)

    • Multi-Repository Migration Package (.axm)

  5. If you selected Repository (.axr) or Migration Package (.axr), configure the following options:

    • Enter the ID of the repository to export in Target Repository ID.

  6. If you selected Multi-Repository Migration Package (.axm), configure the following options:

    • Optionally, enter a comma-separated list of repository IDs in Repositories to Export. Leave the field empty to export all repositories.

    • Select Skip Users to exclude users from the export.

  7. Optionally, enter a password for the exported archive in Archive File Password and Retype Archive File Password.

  8. Configure the database connection parameters as required.

  9. Click Export.

Script Execution​
Remarque

For regular script execution, use Script Execution in the ADOIT Administration. The Operations Tool always executes scripts on the live data and is intended for cases where you are instructed to use it by a BOC employee.

To execute a JavaScript on the application server:

  1. In the Operations Tool, click Script Execution.

  2. Enter the username of an ADOIT administrator in Username.

  3. Enter the corresponding password in Password.

  4. Upload the JavaScript in Script.

  5. Configure the database connection parameters as required.

  6. Click Execute Script.

Attention

Only execute tested JavaScripts that you have received from a BOC employee.

Export Library​
Remarque

You can also export the library in the ADOIT Administration using Export Library.

To export the active library:

  1. In the Operations Tool, click Export Library.

  2. Enter the username of an ADOIT administrator in Username.

  3. Enter the corresponding password in Password.

  4. Optionally, select the language to export in Export Language. Leave the field empty to export all available languages.

  5. Optionally, select the following options:

    • Select Unique Export to export the library with new IDs assigned to all library elements. Use this option only in special cases and if instructed by a BOC employee.

    • Select Skip Library Logs to export the library without library logs. Library logs are used to preserve custom metamodel changes made on the Properties page in the ADOIT Administration when a new application library is imported later. Use this option only in special cases and if instructed by a BOC employee.

    • Select Include Base Library to include the base library in the exported AXL file. The base library is the version of the library on which custom metamodel changes were made on the Properties page in the ADOIT Administration. Use this option only in special cases and if instructed by a BOC employee.

  6. Configure the database connection parameters as required.

  7. Click Export.

Upgrade Product​
Remarque

For the complete upgrade procedure, including the required preparation and post-upgrade steps, see Upgrade ADOIT in the Installation Manual.

The Operations Tool can upgrade the ADOIT database from an older version to version 21.0.

To start the upgrade:

  1. In the Operations Tool, click Upgrade Product.

  2. Enter the username of the database user in DB User Name.

  3. Enter the corresponding password in DB User Password.

  4. Enter the version of ADOIT that you are upgrading from in Source Version.

  5. Enter the password of the ADOIT Admin account in Admin Password.

  6. If you have received an upgrade package from a BOC employee, upload it in Upgrade Package. Otherwise, leave the field empty.

    Remarque

    If you leave Upgrade Package empty, only the component settings are updated, but not the application library. Your component settings are exported before the upgrade and re-imported afterwards, ensuring that your custom configuration is preserved.

  7. Optionally, select the following options:

    • Select Dry Run to perform a test run without applying the upgrade.

    • Select Skip DB Scripts to skip the execution of all database scripts.

  8. Configure the database connection parameters as required.

  9. Click Start Upgrade.

Database Connection Parameters​

The following optional parameters are available for database connections within specific maintenance operation dialogs (such as repository exports). In many environments, these parameters can safely be left empty. The fields are only required depending on your targeted database system and its specific encryption configuration.

  • SSL Mode: For PostgreSQL, allows to specify that an encrypted connection to the database is set up. Possible values are allow, prefer, disable, require, verify-ca and verify-full.

  • SSL Key: For PostgreSQL, specifies the file path to the client SSL key. This is only needed if your database enforces client certificate authentication.

  • SSL Certificate: For PostgreSQL, specifies the file path to the client SSL certificate. This is only needed if your database enforces client certificate authentication.

  • Root Certificate: For PostgreSQL, specifies the file path to the SSL certificate authority (CA) bundle to verify the database server's identity.

  • Trust Server Certificate: For Microsoft SQL Server, specifies whether the server certificate is trusted without validation. Possible values are yes and no.

  • Encryption: For Microsoft SQL Server, specifies the encryption mode for the database connection. Possible values are mandatory, optional and strict.

Remarque

For PostgreSQL, connection encryption configurations are optional. If your database does not strictly demand SSL certificates or secure transport configurations, you can leave all four SSL fields completely blank.

Remarque

For Microsoft SQL Server, encrypted database connections are used by default. If your SQL Server is not configured for encrypted connections, specify optional for Encryption. If your SQL Server uses an encrypted connection with an untrusted server certificate, you may also need to specify yes for Trust Server Certificate.

Initialize the Database​

Use initialize empty database mode to prepare a newly created, empty database for use with ADOIT. In this mode, the Operations Tool starts automatically if the database has been created and the required database tables exist but have not yet been initialized for ADOIT.

Prepare the Database​

Before deploying ADOIT, create the database and execute the required database scripts:

  • For PostgreSQL, execute prepareDB.sql (adapt vDBName and <ADOXX_PASSWORD>) and then postgresql.sql.

  • For Microsoft SQL Server, execute sqlserver_create_db.sql (adapt vDBName and ADOXX_PASSWORD) and then sqlserver.sql.

You can download the database scripts from the BOC Group deployment-examples GitHub repository.

Optional: Change Password of Database User ADOxx​

ADOIT communicates with the database using a dedicated database user. You can use the database user ADOxx or an individual database user.

If you use ADOxx with the predefined default password, you must change the password before proceeding. You can change the password using your database administration tool, for example pgAdmin or SQL Server Management Studio.

Encrypt Database Credentials​

After deploying ADOIT, the Operations Tool starts automatically if the encrypted database user credentials have not yet been provided to ADOIT. Encrypt and provide the database credentials as follows:

  1. In the Operations Tool, click Encrypt Credentials.

  2. Enter the database username in Username.

  3. Enter the corresponding password in Password and Retype Password.

  4. Click Encrypt.

  5. Provide the generated encrypted credentials to the application server through the ADOXX_DBMS_CREDENTIALS environment variable.

Initialize the Database​

Restart the environment. If the database has not yet been initialized, the Operations Tool starts automatically. To initialize the database:

  • In the Operations Tool, upload the required License File.

  • Optionally, upload a Library File if you are using a custom library and select the Primary Language.

  • Configure the database connection parameters as required.

  • Click Initialize Database.

After successful initialization, the Operations Tool shuts down and ADOIT starts normally.

Logging​

The Operations Tool logs its activities according to the logging configuration of the application server. You can configure logging using the ADOXX_LOG_MODE and ADOXX_LOG_DIR environment variables.

The Operations Tool creates a separate log file with the following naming scheme:

yyyy.MM.dd_hh.mm.ss_PID_aoperations.log

Each log entry uses the following format:

yyyy-MM-dd hh:mm:ss.SSS [INFO/WARN/ERROR] [T:AOPERATIONS]

Programs started by the Operations Tool, such as maintenance operations, write their own log files in addition to the Operations Tool log. Their output is not included in the Operations Tool log.

Remarque

All IP addresses that access the Operations Tool are logged in unencrypted form.

Repository Statistics​

View information about your ADOIT deployment. To open the repository statistics:

  • Go to Home > More options, and then click Repository Statistics.

The Scenario Data window opens. The following data is displayed:

  • Product Information: Details about the product, including name, version, platform version, and database schema.

  • General Information: Information about the database, application libraries, repositories, current repository and application library, and available UI languages.

  • User Information: Data about the number of users, the current user’s username, name, and type.

  • License Information: Details on licensed scenarios, including IDs, user limits, and advanced components with their IDs.

  • Repository Contents: Statistics on repositories, including application library, content languages, primary language, and counts for models, objects, relations, and groups. Detailed breakdowns of the number of instances in the database for each model type, object type, and relation type are also included.

Support Access​

The Support Access functionality allows temporarily enabling BOC employees to access your ADOIT Administration for troubleshooting and support purposes.

Remarque

This feature is only available for SaaS deployments.

Prerequisites​

Before you can activate support access, the following prerequisites must be met:

Activate Support Access​

To activate support access:

  • Go to Home > More options, and then click Activate Support Access.

  • Confirm the activation in the dialogue box that appears.

Once activated, a temporary support user account is created with the following properties:

  • This user belongs to the user group Default group and has access to all repositories.

  • The user has full access to the ADOIT Administration and its components.

When support access is activated:

  • A red message indicating "Support Access is active!" appears in the ADOIT Administration next to the welcome text.

  • An email is sent to the BOC support team confirming the activation, along with deployment details (e.g. URL, username, version, etc.).

  • If IP restrictions are active for the ADOIT Administration, BOC support IP addresses are automatically allowed.

Deactivate Support Access​

To deactivate support access:

  • Go to Home > More options, and then click Deactivate Support Access.

When support access is deactivated:

  • The support user account is not deleted but is disabled.

  • BOC support IP addresses are no longer automatically allowed.

  • An email is sent to the BOC support team confirming the deactivation.

  • The red "Support Access is active!" indicator disappears from the ADOIT Administration.

Remarque

If audit logging is enabled or disabled while support access is active, this does not end support access. The support user is also able to manage audit logging settings.