Page Comparison

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

...

Verify that you are running MediationZone version 8.3.x. 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.
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
name upgrade_variables

Variable

Description

MZ_HOME

This environment variable specifies where the software is installed.

Note

...

Note!

You should use an absolute path instead of a symlink for the MZ_HOME directory to avoid any issue during installation or upgrade.

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

Info

title	Example - Setting environment variables

Code Block

language	text
theme	Eclipse

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

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 system restore.
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
title 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.

If you are upgrading from 8.3.x, it is important to make a backup of MZ_HOME for system restore in case of upgrade failure.

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 system restore in case upgrade failure.

Info

title	Use of Filebase persistence

When you have the platform property mz.userserver.filebased set to true, to ensure a seamless upgrade process, it is imperative to export all the config before the upgrade and re-import it afterward. Failure to do so may result in the missing configuration data in the upgrade.

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
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.
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.
Copy the MZ license file into the release content directory.
Info
If you are upgrading from 8.3.x, you need a new license file . Contact DigitalRoute Support on getting the MZ license file.
Code Block
$ cp mz.license <release content directory>
Info
title Example - Copy the mz.license file into installation folder
Code Block
language text
theme Eclipse
$ cp mz.license DR_Internal_9.0.1.0_demo_all_20230616-041603/

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.

Page Properties

hidden	true

Scroll ignore

scroll-viewport	true
scroll-pdf	true
scroll-office	true
scroll-chm	true
scroll-docbook	true
scroll-eclipsehelp	true
scroll-epub	true
scroll-html	true

The install.xml file will automatically be populated with the following information from your existing installation (if the database is SAP HANA):
- install.admin.password
- mz.jdbc.user
- mz.jdbc.password
- mz.jdbc.url
- install.db.jdbc.user
- install.db.jdbc.password
- install.sap.ssl.encrypt - If value is set to true then the following parameters must be manually set
  - install.sap.ssl.truststore
  - install.sap.ssl.truststorepassword
  - install.sap.ssl.hostnameincertificate

Note

title	Note!

Refer Updating the Installation Properties for Platform to know more about these properties and their default values.

Insert excerpt
Upgrade Platform Container
Upgrade Platform Container
nopanel true

Excerpt

name	Important

Warning

title	Important!

If your existing MZ_HOME platform database is configured to use other database type rather than the default Derby, you need to check and update the respective database related properties from the install.xml file to match your current setup.

Oracle

The following properties require manual update:

See Properties for Oracle for details.

PostgreSQL

The following properties require manual update:

See Properties for PostgreSQL for details.

SAP HANA

See Properties for SAP HANA for details.

Note

title	Important Note on Database 3pp Before Upgrading!

If you are upgrading from 9.0.0.0, 9.0.1.0 or 9.1.0.0, check to see if the database 3pp jar is in the $MZ_HOME/3pp folder.

If it does not exist in the $MZ_HOME/3pp folder, then you need to manually copy the database 3pp jar to the $MZ_HOME/3pp folder prior to the upgrade.

This step is NOT required if your current running version is 9.0.2.0 or 9.1.2.0 onwards.

Note

title	Note on Oracle ojdbc.jars!

If you are upgrading from 8.x and using Oracle as the system database, you need to use Oracle 19c (19.20.0.0) JDBC drivers (ojdbc8.jar/ojdbc10.jar).

Replace the jar files in $MZ_HOME/3pp and $MZ_HOME/lib folders

The jar file can be downloaded from https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html

Versions Compared

Old Version 100

New Version 101

Key

Note!