2.4 Installing a New Release

In this scenario, the user wants to install a new release. The configuration space functionality can be used as part of the release process.

  1. The user creates an empty space using the spacecreate command. In this case, the space is named 'preprod'.

    Content of both spaces after the preprod space has been created

  2. The user copies the contents of the active space to the preprod space using the command spacecopy active preprod. This makes the preprod space an exact copy of the active space and ensures that formats from the active space are not lost.

    Content of the preprod space and the active space after the active space has been copied

  3. The user performs a systemimport or vcimport of the configurations which are to be put into production into the preprod space, e g using the command mzsh mzadmin/password @preprod systemimport my-new-config.zip. The imported configuration may originate from an export made from a QA environment after successful testing.

    Content of the preprod space and the active space after a system import has been executed into the preprod space

  4. The user can then login to the Desktop in the preprod space and make any product specific modifications or verify the imported configuration.
     
  5. Before copying the modified passive space to the active space, it is recommended that the user creates a backup space. This means there is a backup copy of the active space if it is required to revert to the previous version of the configurations. The user creates an empty space, e g spacecreate backup.

    Content of the preprod, active and backup spaces after the backup space has been created

  6. The user copies the contents of the active space to the backup space using the command spacecopy active backup.

    Content of the preprod, active and backup spaces after the active space has been copied to the backup space

  7. The workflows running in the active space, except workflows running on ECSA, need to be stopped and unprocessed data must be drained before the preprod space is copied to the active space.

  8. The user copies the contents of the preprod space to the active space using the command spacecopy preprod active.

    Content of the preprod, active and backup spaces after the preprod space has been copied to the active space

  9. If there is an issue in the active space when running the upgraded version, the user can rollback to the previous version. See 2.3 Rollback of a Space.