Versions Compared

Old Version 31

changes.mady.by.user Wei Siong Siow

Saved on

compared with

New Version Current

changes.mady.by.user Huey Yun Ng

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 38

Follow the steps in this section to upgrade the Platform Container.

...

Excerpt


Warning
titleImportant!

When upgrading to 9.x, install.admin.password must be set according to your current admin password before proceeding with the ./setup.sh upgrade step.


Warning
titleImportant!

If the existing installation has additional JVM argument configured before, you need to check if there are obsoleted arguments configured which are obsolete in Java 17. You must remove them if there are obsoleted, remove them and update to use supported options.

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.


Note
titleNote!

When upgrading to 9.x, the install.security property (in install.xml) is automatically set to true. If you prefer to disable this setting, it must be manually changed to false. 

If install.security was set to false before the upgrade and is set to true after or during the upgrade, you need to change the url in the desktop launcher from http to https.



  1. Enter the release content directory that was created when you extracted the delivered *.tgz file during the Preparations, and execute the upgrade.

    Code Block
    themeEclipse
    $ ./setup.sh upgrade


  2. When using the setup.sh upgrade command, setup log file will be generated in the $MZ_HOME/log directory.

    Tip
    titleHint!

    It may be a good idea to open a new command line window in order to keep track of the log files.


  3. Start the pico for the User Interface.

    Code Block
    themeEclipse
    $ mzsh topo set -l pico:ui template:mz.standard-ui
$ mzsh startup ui


  4. MZ 9 upgrade does not install the legacy Web Desktop by default. If this feature is still required, see Installing Web Desktop Server


In case the upgrade was unsuccessful, check the latest setup log for further details in order to analyze the result and see what may have caused the problem. If it is needed, a system restore can be performed. For information about how to perform a system restore, see Simplified Downgrade Procedure.

...