Skip to content

Setup Managed

For all customers who want to run in their own environment, Managed is available.

Installation & Startup Package

Please carry out the installation by following the steps below:

  1. Verify server prerequisites
  2. Installation
  3. Customize configuration
  4. Startup Managed
  5. Recommended activities after installation

Usefull activities to operate Managed: 1. Shutdown Managed 1. Backup & restore Managed data


Supported operating systems and sizing

The following operating systems are supported:

  • Ubuntu
  • Red Hat
  • Fedora
  • Debian

The following sizing depending on the usage is recommended: setup-system-requirements

Software components

The installer assumes that the following software components are already installed on the host:

  • TAR & GZip
  • WGET
  • OpenSSL (not necessary if own SSL certificates are available)
  • Docker & Docker Compose
    • Docker (>= version 20.10.0)
    • Docker-Compose (>= version 1.24.0)


Your contact will provide you with a link to download the Managed core. The installer can be downloaded and executed with the following commands. After the installation you will find the application files in /opt/ and the data files in /home/

wget -nv -N --no-check-certificate https://<my-link> // your get authentification from contact


Command: Download and install managed core

Before the first start or when updates are available, the Docker images must be download once. With the following script the Docker images can be download. Please note that you must register for this in advance.

docker login // your get authentification from contact


Command: Download docker images


Environment variable

The following environment variables can be set to accommodate customer specific wishes, when starting

Environment variable Purpose of use Description Default value
VERSIO_DOMAIN Web server config Define the URL domain address under which the browser user interface can be accessed on the network. The domain address must match the domain specified in the SSL certificate, otherwise the browser will display an error message. Host name
VERSIO_PORT_HTTPS Web server config Define the port on which can be accessed via HTTPS. 443
VERSIO_PORT_HTTP Web server config Define the port on which should be accessible via HTTP. Please note that the HTTP has to be enabled in 'docker-compose.yml'. 80
VERSIO_VALIDITY_CERTIFICATE Self generated SSL certificates Validity of self-generated SSL certificates in days. 365
VERSIO_DATA server and Define the folder to store all logging and database data. /home/
VERSIO_LOGGING_FOLDER server Define the folder to store logging data. /home/
VERSIO_BACKUP_FOLDER Define the folder to store backup data. /home/
VERSIO_STAGE server Define the stage and logging behavior of the instance. If the value is not equal to production or loadtest, the amount of logged information is increased.

Configuration: Environment variables with default values

SSL certificate

The startup script automatically generates an SSL certificate for HTTPS support if no certificate authority is available in the ./ssl folder (ca-root.pem and ca-private-key.pem).

For productive systems we recommend to store company specific SSL certificates in the ./ssl/versio.reverse-proxy folder of the startup script with following file names: * cert-private-key.pem for the private key * cert-public-key.pem for the public key

Please note that for self generated SSL certificates the certification authority 'ssl/ca-root.pem' should or must be made known on the client side:

  • Browser: Import of the certification authority into the certificate memory of the browser. If this is not done, you will receive a browser warning where you can again indicate that you accept the risk.
  • API usage: Announcement of the certification authority to the operating system or manual specification when starting the corresponding client application.


If the installation is finished, the Docker images are available and your customizing is ready, the instance can be started:


Command: Start instance

Enclosed is a sample output for starting a instance: Managed Installer

Image: Managed installer

After successful installation, we recommend that you perform the following activities as soon as possible:

  1. Login with the default user and password
  2. Configure SMTP server for e-mail notification (necessary for initial password set/reset!)
  3. Create new admin user (see Environment settings - User & rights)
  4. Deactivate default admin user
    • Change default password
    • Remove from default environment (see Environment settings - User & rights)
  5. Create a new environment (see Server settings - Environment settings)
  6. Invite new user to the new environment (see Environment settings - User & rights)
  7. Install an OneImporter (see Environment settings - OneImporter - Install)
  8. Configure OneImporter configuration (see Environment settings - OneImporter - Configurations)

Shutdown Managed

To shut down a instance the corresponding command must be executed:


Command: Stop instance

Then, for example, updates of Docker images or other maintenance work can take place before is started again.

Backup & restore Managed data

To backup a server instance with all environment data the corresponding command must be executed (see environment varibale VERSIO_BACKUP_FOLDER):


Command: Backuup instance includes all environment data

The backup script creates a physical backup with name<date>-<time>.tar.gz. Physical backups are performed by copying the individual data files or directories (see logical versus physical backups).

To ensure data integrity, the Server instance is stopped, the backup is performed and the Server instance is restarted. This means that during this time the Server is not available. The downtime depends on the data volume to be backed up and is displayed at the end of the backup execution.

It is recommended to run the backup continuously e.g. based on cron jobs:

40 0 * * * /opt/

Configuration: Cronjob configuration for daily backup

To restore all Managed data you can execute the follwoing script. Please note - All data of the current Managed Instance will be overwritten!!!

bash /opt/ <backup-date-time>

Configuration: Cronjob configuration for daily backup

Please note that a repocessing of the full-text search and topology detection reprocessing for each (!) environment must be performed when restoring backup data:

  • see Environment Settings - Full-text search - Reprocess environment
  • see Environment Settings - Topology detection - Reprocess environment