Versions Compared

Old Version 32

changes.mady.by.user Yeok Hong Ng

Saved on

compared with

New Version 33

changes.mady.by.user Yeok Hong Ng

Saved on

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 for more information.

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 argument configured prior to upgrade from 8.3, you need to check if they are obsolete in Java 17 and in that case remove them.

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
    titleHint!

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

  3. Startup the platform.

    Code Block
    $ mzsh startup platform

  4. If you are upgrading from 8.3, you have to 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.

Info

Example - Output in the upgrade_<timestamp>.log file with invalid configurations.

Code Block
languagetext
Mon Nov 19 10:52:10 CET 2013 Regenerating configs 
The following configurations changed status 
and may require manual attention: 
Workflow Test.WF1 became invalid, 
Workflow Test.WF2 became invalid, 
APL Code Test.apl_profile became invalid,