Page Comparison

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 running version 8.3.0.0 or later. 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. If the system is running an earlier version, you need to upgrade it to an 8.3.x version first. See the documentation space for the version you are currently running for more information.
     

2. Install either Oracle JDK 17 or OpenJDK 17 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:
   

$ export MZ_HOME=/opt/mz 
$ export JAVA_HOME=//Library/Java/JavaVirtualMachines/jdk-17.0.2.jdk/Contents/Home
$ export PATH=$JAVA_HOME/bin:$MZ_HOME/bin:$PATH

5. Make a backup of all your configurations with System Export. This can be done either in Desktop, which is described in System Exporter or by using the mzsh systemexport command:

   Code Block
   $ mzsh mzadmin/<password> systemexport <backup directory>/<filename>

   Info
   title Use of System Export File
   The exported configurations might be needed in order to be able to perform a downgrade.

6. Make an online backup of the database(s). For further information regarding how to perform an online backup, see Preventive Maintenance Procedures.
   Note! If you are upgrading from 8.3.x, you can find the database backup instructions in the documentation for 8.3 as the procedure may differ from that of 9.x.

7. If you are upgrading from 8.x, 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
   title Note!
   Ensure that you have shutdown your platform and all executions prior to the backup.

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

   Info
   title Use of MZ_HOME backup
   The MZ_HOME backup might be needed in order to be able to perform a rollback in case upgrade failure.

8. If you are performing an upgrade of a system with large configurations, you may need to increase the maximum number of file descriptors.

   Info
   title Example - Changing the maximum number of file descriptors on Linux
   Code Block language text theme Eclipse $ cat /proc/sys/fs/file-max 5000 $ su - root Password: $sysctl -w fs.file-max=100000

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

   Note
   title Note!
   The staging directory should not be the same directory as the one you created and set up as the MZ_HOME directory.

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

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

    Code Block
    $ 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.
    

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

    Code Block
    $ cp mz.license <release content directory>

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

    Code Block
    $ cd <release content directory> $ ./setup.sh prepare

    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.