The installation process of the Extended DMS has been redesigned. If you are looking for information in relation to the old DMS installation process. please follow the pages marked "DEPRECATED" in the hierarchy. Some information in these pages may be useful in case of issues with the setup, however, the following process should be complete to get your DMS installation up and running smoothly


Ubuntu 22 LTS ova

Since May 2022 we recommend to use Ubuntu 22 LTS ova image for VMware ESXI 6.5+ environment

Ubuntu 22 installed in a 100GB partition with the following components/settings:

  • Kernel 5.15
  • git v2.34
  • Docker 20.10.15
  • User "dms" with sudo rights and PI SSH keys allowed to login
  • NTP Enabled, please make sure to change it to your timezone
  • Pre-installed auto-deploy scripts

The locale/timezone settings can be changed as needed, the auto-deployed scripts can be updated by pulling from the git repositories.


  1. To start with, please download our pre-configured .ova image for VMware ESXI 6.5+ environments or pre-configured .vmdk disk image.

  2. Create a VM using the image, start up and perform the necessary network base settings (default is DHCP which is generally unsuitable for a DMS server appliance).
    Open the Activities overview and start typing Settings. Click on Settings. If you plug in to the network with a cable, click Network, otherwise click Wi-Fi. Click the settings button. Select the IPv4 or IPv6 tab and change the Method to Manual. It is suggested that you set your network to static IP. Remember to also set addresses for your internal DNS server. You can find some help, e.g. here.

    After you set your network settings as required, please restart the network service:

    Ubuntu network restart
    sudo systemctl restart networking

    After that, reboot the host. Your network is now ready to use with the parameters you set.

  3. If there is no ssh key (~/.shh/), create a ssh key using

    ssh-keygen -t ed25519

    which creates a unique pair of public/private keys for your environment. Use default values, if possible. If you have to name your key-file differently than "id_rsa", please see below.

  4. Then send the "~/.ssh/id_ed25519.pub" file from ~/.ssh/ to Patrix and/or PI to set up authenticated access to your client specific repository holding your setup configuration.
  5. Assign a FQDN to the static IP of your DMS server in your DNS server.
  6. Make sure that /etc/timezone file exists and locale is set appropriately (eg. Europe/Berlin)
    for setting your timezone on the OVA (Ubuntu 22 LTS ova) use sudo timedatectl set-timezone your_time_zone and make sure that your_time_zone is valid.
  7. From thereon, you should be able to continue with our auto-deploy technology: Click here to continue.


Note: If you are using the DMS with a storage mount point to hold your repository data, to ensure proper functioning after a host reboot, you should modify the docker configuration so as to make sure docker is only started once the storage out point has become available to the host. Please read systemd documentation for further information.


Requirements for EDMS in ubuntu systems - server side


0-40 users40-150 users
CPU16 cores32 cores
RAM48GB96GB
Disc Size3x the folder size of documents3x the folder size of documents
Shards

10-50G of index size per shard

~ 10 shards

10-50G  of index size per shard

~ 10 -30 shards

Replicasno replica1 replica

Note: These are estimated configuration values, they can vary from system to system. For systems with 150+ users, a separate investigation regarding their needs and therefore requirements should be done. The RAM values should always be increased, if the capacity is approaching its maximum. Otherwise, the proper functionality of the system can not be guaranteed. Furthermore, please note, that the number of shards is in general depending on the size of the index. Per 10-50G of Index, one shard is recommended. The number of shards should be increased in steps of 10.

CentOS 7 pre-configured image

Since May 2022 we recommend to use Ubuntu 22 LTS ova image for VMware ESXI 6.5+ environment. See section above


  1. To start with, please download our pre-configured .ova image for VMware ESXI 5.5+ environments (also available as .vmdk image). For Hyper-V environments, please download our pre-configured .vhdx image. For Xen Server, please download or pre-configured Xen-compatible image for importing into Xen. Similar templates for other virtualization platforms may be available on request.

  2. Create a VM using the image, start up and perform the necessary network base settings (default is DHCP which is generally unsuitable for a DMS server appliance). Set your network settings by running "nmtui". It is suggested that you set your network to a static IP. Remember to also set addresses of your internal DNS server. You can find some help, e.g. here.

    After you set your network settings as required, please restart the network service:

    systemctl restart network.service

    After that, reboot the host. Your network is now ready to use with the parameters you set.

  3. Assign a FQDN to the static IP of your DMS server in your DNS server.

  4. Make sure that /etc/timezone file exists and locale is set appropriately (eg. Europe/Berlin)
  5. for setting your timezone on the OVA (CentOS 7) use timedatectl set-timezone your_time_zone and make sure that your_time_zone is valid.

  6. Create a ssh key using

    ssh-keygen -t rsa

    which creates a unique pair of public/private keys for your environment. Use default values, if possible. If you have to name your key-file differently than "id_rsa", please see below.

  7. Send the "id_rsa.pub" file from ~/.ssh/ to Patrix and/or PI to set up authenticated access to your client specific repository holding your setup configuration.

  8. From thereon, you should be able to continue with our auto-deploy technology: Click here to continue.

Note: If you are using the DMS with a storage mount point to hold your repository data, to ensure proper functioning after a host reboot, you should modify the docker configuration so as to make sure docker is only started once the storage out point has become available to the host. Please check here for further information.

Pre-configured centos .ova configuration

CentOS 7 installed in a 100GB partition with the following components/settings:

  • Kernel 3.10
  • git with 2.10.1
  • Docker 17.05
  • User "dms" with sudo rights and PI SSH keys allowed to login
  • NTP Enabled, pre-set locale/timezone Europe/Berlin (CET)
  • Pre-installed auto-deploy scripts

The locale/timezone settings can be changed as needed, the auto-deployed scripts can be updated by pulling from the git repositories.

Make git use different key file than default "id_rsa"

This will not be required under normal circumstances - it is merely given here for special situations and when advised by Patrix or Practice Insight.

If you had to use a different name for your key-file than the default "id_rsa", you can make git use this key file for accessing the client specific repository as follows:

cd into .ssh/ directory and un create file "config" file with following contents:

Host edmssupport.pace-ip.com
IdentityFile ~/.ssh/<private_key_file_name>

<private_key_file_name> should be the key file that you produced using ssh-keygen or copied into the system.

Finally set the security settings on the relevant files as follows:

chmod 600 .ssh/<private_key_file_name> && chmod 600 .ssh/config

replace <private_key_file_name> accordingly.