Maintenance

Upgrade a DMSContainer Instance

DMSContainer can be upgraded easily, following these steps you can upgrade a running instance in a matter of minutes.

  • Download the latest Setup package from download section

  • Stop any running DMSContainer services or debug sessions.

  • Uninstall DMSContainer (this will leave all the config files and databases untouched)

  • Run the downloaded Setup and install it in the proposed folder if possibile.

    • Each setup tries to install DMSContainer in a version specific folder to make it easier to mantain for the end users. If you can stick with default settings.

  • Accepts all the default settings and complete the installation

  • Copy your current dms.license file in the DMS_HOME\license folder

  • Run the DMSContainer service, it should start without any problems. If problem arises check the common solutions section.

By default DMSContainer will run on port 443 as HTTPS service using Self-Signed certificates. If you need different configuration, modify the main config file dmscontainer.config.json.

  • Stop the new DMSContainer instance

  • Copy the old jobspackage\DMS_DATA.FDB file (from the older instance) into the new DMS_HOME\jobspackage\DMS_DATA.FDB

  • Copy the old configuration folder DMS_HOME\conf (from the older instance) into the new DMS_HOME\conf

  • Restart the new DMSContainer service

  • If no errors occurred you have safely and successfully upgraded your DMSContainer instance.

    In some cases you need to recompile your custom ClassJob

Updating DMSContainer using an hotfix

Updating a running instance of DMSContainer is a bit simpler than upgrading a full instance. No new folder not new installations are needed, just substitute some files. Hofixes are an handy solution for quick and light updates.

  • Download the latest update pack package from download section.
    • Un update pack has a name similar to dmscontainer_<version>_hotfix.7z
  • Do a full backup of your DMSContainer instance (in case you are updating a production instance).
  • Stop any running DMSContainer services or debug sessions.
  • Unzip the update pack and overwrite all the DMSContainer files with the files available in the 7zip (just overwrite the folder DMS_HOME).
  • Restart the service and check the logs for errors.
  • If no errors occurred you have successfully updated your DMSContainer instance.

While an upgraded installation is completely new installation, an updated one if just “updated” so some names and path are still using the old names while using the new files. To be sure about what’s your installed version check the file DMS_HOME\VERSION.TXT which contains the latest info about your version.

Cold Backup

DMSContainer is robust, fast and self contained. Maintaining a DMSContainer instance is really simple. Here’s some common best practices useful to face with the day by day needs when is running DMSContainer.

DMSContainer itself and the built-in modules store their data in specific folders. There are the steps to safely backup your data and configurations.

  • Stop DMSContainer
  • Backup file DMS_HOME\jobspackage\DMS_DATA.FDB coping it in a safe place
  • Backup folder DMS_HOME\conf coping it in a safe place
  • Restart DMSContainer

Hot Backup

I you cannot stop DMSContainer to do a backup, you can use the following procedure

  • Open command prompt and navigate to DMS_HOME
  • Run DMSBACKUP.BAT mybackupfile.dmsbck
  • Backup folder DMS_HOME\conf coping it in a safe place

Back to Getting Started