Page Comparison

...

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


Set the environment variables:

Insert excerptPreparationsPreparationsnopaneltrue Info

title	Example - Setting environment variables

Code Block

language	text
theme	Eclipse

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

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

2. Once you have prepared the install.xml file, edit the following:
   

   Info
   title Example - Editing the install.xml file
   Note title 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.

Info

title	Example - Setting environment variable IGNORE_TAR_EXIT

Code Block
language text theme Eclipse
$ 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
language text theme Eclipse
$ tar xvf <licenseName>.tar

Info

title	Example - Extracting the upgrade software

Code Block
language text theme Eclipse
$ tar xvf MZ8.0.tar

The setup script for the new version of  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:

Code Block
language text theme Eclipse
$ ./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.

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

...

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 /wiki/spaces/MD82/pages/3778612 in the /wiki/spaces/MD82/pages/3778529.

...

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.

1. Ensure that the value install.type for 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. Code Block <property name="install.types" value="ec"/> <property name="pico.rcp.platform.host" value= ""/> <property name="pico.rcp.platform.port" value= "6790"/> <property name="pico.rcp.server.host" value= ""/> <property name="mz.webserver.port" value= "9000"/> <property name="install.security" value= "true"/>

   
   

2. Execute the upgrade.

   Code Block
   $ ./setup.sh

...

1. upgrade