Versions Compared

Old Version 1

changes.mady.by.user Jenni Wallin

Saved on

compared with

New Version 2

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

  2. Set the environment variables:

    Insert excerpt
    6.2 Preparations
    6.2 Preparations
    nopaneltrue

    Info
    titleExample - Setting environment variables


    Code Block
    languagetext
    themeEclipse
    $ export MZ_HOME=/opt/mz 
$ export JAVA_HOME=/opt/jdk/jdk1.8.0_121
$ export PATH=$JAVA_HOME/bin:$MZ_HOME/bin:$PATH



    Note
    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.

    Info
    titleExample - Setting environment variable IGNORE_TAR_EXIT


    Code Block
    languagetext
    themeEclipse
    $ export IGNORE_TAR_EXIT=true



      

  3. 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


    Info
    titleExample - Extracting the upgrade software


    Code Block
    languagetext
    themeEclipse
    $ tar xvf MZ8.0.tar


    The setup script for the new version of  will of the software will be extracted in the directory you are located in when executing the command.

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

    Code Block
    languagetext
    themeEclipse
    $ ./setup.sh patch


  5. Enter user name the username and password at the prompt.

  6. 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.


  7. Repeat steps 1 to 6 for each Execution Container that you want to upgrade.


Tip
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.

PropertyDescription

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.


Info
titleExample - Setting properties in setup.sh
$ ./setup.sh patch -Dmz.username=mzadmin -Dmz.password=<password>