6.6 Upgrade Execution Container

Follow the steps in this section to upgrade an Execution Container.

Copy the *.tar file with the upgrade software to the Execution Container host.

Set the environment variables:

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

If the Execution Container is located on the same host as the Platform Container, proceed to step 4. If the Execution Container is located on a separate host, extract the software:
```
$ tar xvf <licenseName>.tar
```
Example - Extracting the upgrade software
$ tar xvf MZ8.0.tar
The setup script for the new version will be extracted in the directory you are located in when executing the command.
Use the setup script setup.sh to upgrade the Execution Container:
```
$ ./setup.sh patch
```
Enter user name and password at the prompt.
Enter the path to the Platform web interface at the prompt, e g http://platform1:9000, and the upgrade will start.
By default, the script validates that the Platform Container can connect to the Execution Container and then enables remote access.
Repeat steps 1 to 6 for each Execution Container that you want to upgrade.

Hint!

You can use the following properties with setup.sh to modify the behavior of the script. This is is useful e g when you want to automate the upgrade procedure or when network conditions prevent validation of the connection between the Platform Container and the Execution Container.

Property	Description
mz.username	Default: "" Set username and disable the prompt.
mz.password	Default: "" Set password and disable the prompt.
install.str.remote.enabled	Default: `true` Enable remote access to the Execution Container. For information about enabling remote access after the installation, see 2.2 Remote Access to Containers in the System Administrator's Guide.
install.str.remote.ping.disabled	Default: `false` Disable validation of Platform connection to Execution Container before enabling remote access. The default value is `false`.
install.str.remote.ping.timeout	Default: `5000` Set timeout limit for validation of Platform connection in milliseconds.
mz.platform	Default: "" Set the URL for the Platform web interface and disable the prompt.

Example - Setting properties in setup.sh

$ ./setup.sh patch -Dmz.username=mzadmin -Dmz.password=<password>

Next:

6.7 Post Upgrade