Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Follow the steps in this section to upgrade an Execution Container.

...

Set the environment variables:

Excerpt

...

...

titleExample - Setting environment variables
Code Block
languagetext
themeEclipse
$ export MZ_HOME=/opt/mz 
$ export JAVA_HOME=/opt/jdk/jdk-17.0.2
$ export PATH=$JAVA_HOME/bin:$MZ_HOME/bin:$PATH 

...

titleNote!

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.

...

titleExample - Setting environment variable IGNORE_TAR_EXIT
Code Block
languagetext
themeEclipse
$ 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:

Code Block
languagetext
themeEclipse
$ tar xvf <licenseName>.tar

...

titleExample - Extracting the upgrade software
Code Block
languagetext
themeEclipse
$ tar xvf MZ8.0.tar

...

Use the setup script setup.sh to upgrade the Execution Container:

Code Block
languagetext
themeEclipse
$ ./setup.sh patch

...

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.

...

titleHint!

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.

...

mz.username

...

Default: ""

Set username and disable the prompt.

...

Default: ""

Set password and disable the prompt.

...

Default:  true

Enable remote access to the Execution Container. For information about enabling remote access after the installation, see Remote Access to Containers.

...

Default: false

Disable validation of Platform connection to Execution Container before enabling remote access. The default value is false.

...

Default: 5000

Set timeout limit for validation of Platform connection in milliseconds.

...

Default: ""

Set the URL for the Platform web interface and disable the prompt.

...

namejvm-arguments-note
Info

Important!

If the existing installation has additional JVM arguments configured which are obsolete in Java 17, remove them and update to use supported options.

Please refer to Java 17 docs for details on ‘Obsolete’ and ‘Removed’ Java options since Java 8.

See Managing Picos with Topo for JVM Arguments configuration.

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

  1. Before proceeding with the upgrade, you are required to perform backups, copy the MZ license file to the release directory and prepare the install.xml file. For more information, refer to Upgrade Preparations.

Note

Note!

Ensure that the value for install.type is set to ec when upgrading the Execution Container. 

These properties should be configured according to the platform container setup. For more information, refer to Execution Container Properties.

  1. Execute the upgrade.

    Code Block
    languagetext
    $ ./setup.sh 

...

  1. upgrade