6.2 Preparations

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.

Note!

For users who have custom agents created in Development Toolkit:

If you have custom agents created using Development Toolkit, these agents cannot be included in the upgrade. For information on how to remove them before proceeding with the upgrade procedure, see Upgrade and Downgrade in 2. Installation and Setup in Development Toolkit User's Guide.

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/jdk1.8.0_121
$ export PATH=$JAVA_HOME/bin:$MZ_HOME/bin:$PATH

Note!

If the software is installed on a GlusterFS storage, you must also set the environment variable IGNORE_TAR_EXIT to true. This will suppress non-critical errors that are caused by the tar command during upgrade. If these errors are not suppressed, the upgrade process will abort.

Example - Setting environment variable IGNORE_TAR_EXIT

$ export IGNORE_TAR_EXIT=true

Make a backup of all your configurations with System Export. For further information regarding System Export, see 6.12 System Exporter in the Desktop User's Guide.
```
$ mzsh mzadmin/<password> systemexport <backup directory>/<filename>
```
Note!

The exported configurations might be needed in order to be able to perform a downgrade.
Make an online backup of the database(s). For further information regarding how to perform an online backup, see 7. Backup and Disaster Recovery Procedures in the System Administrator's Guide.
If you are performing and upgrade of a system with large configurations, you may need to increase the maximum number of file descriptors.
Example - Changing the maximum number of file descriptors on Linux
$ cat /proc/sys/fs/file-max 5000 $ su - root Password: $sysctl -w fs.file-max=100000
Unzip the upgrade software file:
```
$ gunzip <licenseName>.tgz
$ tar xvf <licenseName>.tar
```
Example - Extracting the upgrade software
$ gunzip MZ8.0.tar.tgz $ tar xvf MZ8.0.tar
The release content directory structure and the setup script, setup.sh, for the new version will be extracted in the directory you are located in when executing the tar command.
If you are running services on SCs, and want to minimize downtime, leave the SCs running during the upgrade procedure.
When you are upgrading from 7.3, you can find the value of MZ_CONTAINER in MZ_HOME/bin/mzsh. If the assigned value to MZ_CONTAINER is not unique in your system, you must update it.
```
$ cat $MZ_HOME/bin/mzsh
```
Example - Value of MZ_CONTAINER
. . . if [ -z "${MZ_CONTAINER+x}" ]; then MZ_CONTAINER="platform1" export MZ_CONTAINER fi . . .
For the Platform container, if you have downloaded the jar files yourself, make sure to update the jar files in your 3pp folder: $MZ_HOME/3pp.

Next:

6.3 Disconnect ECSAs