Upgrade Execution Container

Important!

If the existing installation has additional JVM argument configured before, you need to check if there are obsoleted in Java 17. You must remove them if there are obsoleted.

Refers to Managing Picos with Topo for JVM Arguments configuration.

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:

Important!

If your existing MZ_HOME platform database is configured to use other database type rather than the default Derby, you need to check and update the respective database related properties from the install.xml file to match your current setup.
Oracle
The following properties require manual update:
<property name="install.ora.jdbc.user" value="mzadmin"/>
<property name="install.ora.jdbc.password" value="mz"/>
<property name="install.ora.owner" value="mzowner"/>
<property name="install.ora.password" value="mz"/>
<property name="install.ora.host" value="localhost"/>
<property name="install.ora.size" value="small"/>
<property name="install.ora.port" value="1521"/>
<property name="install.ora.home" value="/opt/oracle"/>
<property name="install.ora.sid" value="MZ"/>
See Properties for Oracle for details.
PostgreSQL
The following properties require manual update:
<property name="install.pg.owner" value="mzowner"/>
<property name="install.pg.password" value="mz"/>
See Properties for PostgreSQL for details.
SAP HANA
See Properties for SAP HANA for details.
Important Note on Database 3pp Before Upgrading!

If you are upgrading from 9.0.0.0, 9.0.1.0 or 9.1.0.0, check to see if the database 3pp jar is in the $MZ_HOME/3pp folder.
If it does not exist in the $MZ_HOME/3pp folder, then you need to manually copy the database 3pp jar to the $MZ_HOME/3pp folder prior to the upgrade.
This step is NOT required if your current running version is 9.0.2.0 or 9.1.2.0 onwards.
Note on Oracle ojdbc.jars!

If you are upgrading from 8.x and using Oracle as the system database, you need to use Oracle 19c (19.20.0.0) JDBC drivers (ojdbc8.jar/ojdbc10.jar).
Replace the jar files in $MZ_HOME/3pp and $MZ_HOME/lib folders
The jar file can be downloaded from https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html
Example - Setting environment variables
$ export MZ_HOME=/opt/mz $ export JAVA_HOME=/opt/jdk/jdk-17.0.2 $ 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 is extracted into 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 Remote Access to Containers.
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>