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:

  1. To start with, please download our pre-configured .ova image for VMware ESXI 5.5+ environments. For Hyper-V environments, please download our pre-configured .vhdx image. Similar templates for 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. 

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

    systemctl restart network.service

    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. 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.pub", please see below.

  6. 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.

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

    1. Add .ssh/config file with following contents:
Host support.practiceinsight.io
  IdentityFile ~/.ssh/mykey.rsa
2. Add file with encrypted private key (.ssh/mykey.rsa)  using a tool such as WinSCP
chmod 600 .ssh/mykey.rsa
chmod 600 .ssh/config
  8. From thereon, you should be able to continue with our auto-deploy technology: Click here to continue.

Pre-configured .ova configuration

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

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.pub