Release Management

Datamine has a simple release management process.

  • For manual installations there is a requirement to:
    • Follow the uninstall approach indicated in that version of the Installation documentation.
    • Perform an installation using the new version of MOR
  • For Appliance versions it involves updating the Master Offline Repository (MOR) with the latest release and then using the Appliance Manager (VEAM) to upgrade the environment.

Note: Refer to the Patching section in the installation guide for instructions on installing releases.

The levels of release are:

  • Release version—Major changes that make up a new release that includes all patches and any new functionality
  • Patch—An interim release made available to fix specific priority 1 (P1) issues

The CCLAS component applications are designed so that they can be reinstalled without impacting any data or configuration information.

Data is held in the CCLAS Database and Enterprise File System (EFS). If a new deployment changes the data structure or database, then there is a requirement to either:

  • Backup that data/database so that there is a restore point .
  • Duplicate the data/database so that the new copy is used for the new deployment and the original can be pointed to if there is a requirement to back out of the change.

The following strategies are suggested:

  • Ensure that there is an ability to back out
    • The VEAM provides the ability to create any version of CCLAS that is stored in the ‘Master Offline Repository’ (MOR). This provides the functionality to recreate the environment required as part of the back out process. For manual installations the customer must install using the MOR (.mor) file appropriate to the version.
    • The CCLAS Data areas need to be backed up or duplicates made so that the change can be applied to the duplicate. With this strategy backing out requires pointing to the original data as part of reinstalling the previous version servers.
  • Only perform a deployment when
    • Patches only when required.
    • Releases as part of an upgrade to the latest version to include all the latest functionality and patches that are released.

Note: You cannot upload a MOR (.mor) file once a more current release version is loaded.