Upgrade Preparations

Owned by Former user (Deleted)
Last updated: Dec 18, 2024 by Jenni Wallin
3 min read

During the upgrade process, you must use the default application user, mzadmin, and correct password whenever you are prompted to enter it.

The preparation steps will not affect the running system and can be done in advance.

Before proceeding with the upgrade, make the following preparations:

  1. Verify that you are on a version from which upgrade is supported. You can check the current version by opening the About window in the Desktop, where the current version is listed in the Pico Version section. See the documentation space for the version you are currently running for more information.

  2. Install either Oracle JDK 17 or OpenJDK 17 on the server(s) where the Platform Container and Execution Containers are running.

  3. Verify that the System Requirements are met. If the operating system, or database need to be upgraded, this should be done prior to the upgrade. This has to be done for all machines that are hosting the system.

  4. Ensure that the environment variables are set correctly:

Variable

Description

MZ_HOME

This environment variable specifies where the software is installed.

JAVA_HOME

This environment variable specifies where the JDK is installed.

PATH

This environment variable specifies the search path and must contain the following directories:

$JAVA_HOME/bin:$MZ_HOME/bin

Example - Setting environment variables

$ export MZ_HOME=/opt/mz $ export JAVA_HOME=/opt/jdk/jdk-17.0.2 $ export PATH=$JAVA_HOME/bin:$MZ_HOME/bin:$PATH

  1. Make an online backup of the database(s). For further information regarding how to perform an online backup, see Backup and Disaster Recovery Procedures.

Note!

If you are upgrading from 9.x, you can find the database backup instructions in the documentation for 9.x.

  1. It is important to make a backup of MZ_HOME for rollback purposes.

    To make a backup of your MZ_HOME, you can use the following command:

Note!

Ensure that all processes in your installation are shutdown prior to the backup.

You can check which processes are running by using the mzsh status command.

$ cd $MZ_HOME/../ $ tar -zcvf mzhome_backup.tgz <MZ_HOME directory> $ mv mzhome_backup.tgz <backup directory>

  1. Create a directory to use when unpacking this release and future releases. For the purpose of these instructions, this designated directory is referred to as the staging directory.

  1. Place the *.tgz file from your release delivery into the staging directory.

  2. Use a command line tool, go to the staging directory, and unpack the *.tgz file by running the following command:

    $ tar xvzf <filename>.tgz

    A directory is then created in the staging directory, containing the software to be installed. For the purpose of these instructions, this directory is referred to as the release content directory.

  3. Now copy the MZ license file into the release content directory.

  1. Enter the release content directory and prepare the install.xml file by running the following command:

The *.mzp packages have now been extracted, and the install.xml has been extracted into the release content directory. The install.xml file will automatically be populated with information from your existing installation.

Â