Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Important!

It is essential to review and potentially adjust your Java memory settings, especially prior to an upgrade process as it demands additional resources for memory heap, pico timeout and Metaspace size. See Java Configuration and Managing Picos with Topo.

Excerpt
Info

Important!

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

Excerpt
namejvm-arguments-note
Info

Important!

If the existing installation has additional JVM arguments configured which are obsolete in Java 17, 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.

See Managing Picos with Topo for JVM Arguments configuration.

...

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

    Code Block
    $ ./setup.sh upgrade

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

Tip

Hint!

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

  1. Startup the platform.

    Code Block
    $ mzsh startup platform
  2. Start the pico for the User Interface.

    Code Block
    $ mzsh startup ui

    If you wish to change the port number, execute the following command:

    Code Block
    mzsh topo set topo://container:<platform-container>/pico:ui/val:config.properties.ui.webserver.port <port-number>

Note

Note!

If your upgrade fails, you may want to perform a rollback using the old MZ_HOME backup, see Simplified Downgrade Procedure

Note

Note!

If you are using SAP HANA as the Platform database, you will need to enable TLS/SSL on the SAP HANA database after you upgrade your Platform. 

...