Versions Compared

Old Version 67

changes.mady.by.user Yong Chee Keong

Saved on

compared with

New Version Current

changes.mady.by.user Yeok Hong Ng

Saved on

Key

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

...

The preparation steps will not affect the running system and can be done in advance.

Note

Note!

For users who have custom agents created in Development Toolkit and upgrading from MediationZone 8.3:

If you have custom agents created using Development Toolkit, these agents cannot be included in the upgrade. For information on how to remove them before proceeding with the upgrade procedure, see Upgrade and Downgrade in Installation and Setup.

Note

Note!

For systems using Configuration Spaces:

Configuration Spaces is replaced with the new Workflow Packages functionality. Prior to upgrading make sure to export the configuration from inactive configuration spaces that you want to keep, as only the active space is carried across during the upgrade process.

For further information regarding Configuration Spaces, and how to use them, refer to Configuration Spaces in the MediationZone 8.3 documentation.

Before proceeding with the upgrade, make the following preparations:

  1. Verify that you are running version 8.3.x or 9.0.x. You can check the current version by opening the About window in the Desktop, where the current version is listed in the Pico Version section. If the system is running an earlier version, you need to upgrade it to 8.3.x or 9.0.x version first. See the documentation space for the version you are currently running for more information.
      

  2. Install either Oracle JDK 17 or OpenJDK 17 on the server(s) where the Platform Container and Execution Containers are running.

  3. Verify that the System Requirements are met. If the operating system, or database need to be upgraded, this should be done prior to the upgrade. This has to be done for all machines that are hosting the system.

  4. Ensure that the environment variables are set correctly:

Excerpt
nameupgrade_variables

Variable

Description

MZ_HOME

This environment variable specifies where the software is installed.

Note

Note!

You should use an absolute path instead of a symlink for the MZ_HOME directory to avoid any issue during installation or upgrade.

JAVA_HOME

This environment variable specifies where the JDK is installed.

PATH

This environment variable specifies the search path and must contain the following directories:

$JAVA_HOME/bin:$MZ_HOME/bin

...

  1. Create a directory to use when unpacking this release and future releases. For the purpose of these instructions, this designated directory is referred to as the staging directory.

Note

Note!

The staging directory should not be the same directory as the one you created and set up as the MZ_HOME directory.

...