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.
...
title | Example - Setting properties in setup.sh |
---|
...
- Copy the *.tar file with the upgrade software to the Execution Container host.
Set the environment variables:
Insert excerpt Preparations Preparations Before proceeding with the upgrade, you are required to perform backups, copy the MZ license file to the release directory and prepare thenopanel true install.xml
file. For more information, refer to Preparations. Once you have prepared the
install.xml
file, edit with the following:Info title Example - Setting environment variablesEditing the install.xml file 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
Note title Note! If the software is installed on a GlusterFS storage, you must also set the environment variable
IGNORE_TAR_EXIT
totrue
. 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
The setup script for the new version is extracted into the directory you are located in when executing the command.Code Block language text theme Eclipse $ tar xvf MZ8.0.tar
Use the setup script
setup.sh
to upgrade the Execution Container:<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"/>
Execute the upgrade.
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
will start.upgrade
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.
...
title | Hint! |
---|
Note | ||
---|---|---|
| ||
The XML files, including |