Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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.

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

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

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

    Example - Editing the install.xml file

    Note!

    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.

    <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"/>

  3. Execute the upgrade.

    $ ./setup.sh upgrade
  • No labels