Versions Compared

Version Old Version 6 New Version Current
Changes made by

Kevin Wu

Wei Siong Siow

Saved on

Key

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

...

Excerpt
namejvm-arguments-note
Info

Important!

If the existing installation has additional JVM argument configured prior to upgrade from 8.3, you need to check if they arguments configured which are obsolete in Java 17 and in that case , 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.

...

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. If you are upgrading from 8.3, you have to start Start the pico for the User Interface.

    Code Block
    $ mzsh topo set -l pico:ui template:mz.standard-ui
$ 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. 

Note

Note!

If you have HTTP configured in the 8.x platform container prior to the upgrade, the configuration will apply to MediationZone 9 upon upgrade. For more information on configuring the HTTP, see HTTP Configuration Properties.

Tip

Hint!

If any configurations have become invalid due to the upgrade, these will be listed in the log file. Search for the string "Regenerating configs" in the log file to find information about any invalid configurations.

...