...
Verify that you are running a 9.x version before this version. 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 before 9.x, you need to upgrade it to an 9.x version first. See the documentation space for the version you are currently running for more information.
Install either Oracle JDK 17 or OpenJDK 17 on the server(s) where the Platform Container and Execution Containers are running.
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.
Ensure that the environment variables are set correctly:
| Excerpt | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
...
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.
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 |
|---|
NoteImportant! Ensure that all processes in your installation are shutdown prior to the backup. You can check which processes are running by using the |
| Code Block |
|---|
$ cd $MZ_HOME/../ $ tar -zcvf mzhome_backup.tgz <MZ_HOME directory> $ mv mzhome_backup.tgz <backup directory> |
Note!
Use of MZ_HOME backup
The MZ_HOME backup is needed in case the upgrade fails.
| Info |
|---|
Use of Filebase persistenceWhen you have the platform property |
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 |
|---|
| Note Important! The staging directory should not be the same directory as the one you created and set up as the MZ_HOME directory. |
Place the *.tgz file from your release delivery into the staging directory.
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.
Now copy the MZ license file into the release content directory.
...
Note!
If you are upgrading from an earlier major or minor version, you need a new license file. https://www.digitalroute.com/contact/contact-support/ on getting the MZ license file.
| Code Block |
|---|
$ cp mz.license <release content directory> |
...
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.
...
Note!
...
...
for more information about these properties and their default values.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
| Excerpt | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...