...
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 in /wiki/spaces/MD82/pages/3779155. |
| 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, please refer to Configuration Spaces in the |
Before proceeding with the upgrade, make the following preparations:
Verify that you are running version 8.3.x or 9.0.0 or laterx. 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 an 8.3.x or 9.0.x version first. See the documentation space for the version you are currently running for more information.
Install either Oracle JDK 17 or OpenJDK 17 on the server(s) where the Platform Container and Execution Containers are running.
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.
Ensure that the environment variables are set correctly:
| Excerpt | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
| Info |
|---|
...
Example - Setting environment variables
|
...
...
|
...
|
...
|
Make
...
| Code Block |
|---|
$ mzsh mzadmin/<password> systemexport <backup directory>/<filename> |
| Info | ||
|---|---|---|
| ||
The exported configurations might be needed in order to be able to perform a downgrade. |
...
an online backup of the database(s). For further information regarding how to perform an online backup, see
...
| Note |
|---|
Note! If you are upgrading from |
...
9.x, you can find the database backup instructions in the documentation for 8.3 as the procedure may differ from that of 9.x. |
...
It is important to make a backup of MZ_HOME for rollback purposes.
To make a backup of your MZ_HOME, you can use the following command:
| Note |
|---|
...
Note! Ensure that |
...
all processes in your installation are shutdown prior to the backup. You can check which processes are running by using the |
| Code Block |
|---|
$ cd $MZ_HOME/../
$ tar -zcvf mzhome_backup.tgz <MZ_HOME directory>
$ mv mzhome_backup.tgz <backup directory> |
| Info |
|---|
...
Use of MZ_HOME backupThe MZ_HOME backup |
...
is needed in |
...
If you are performing an upgrade of a system with large configurations, you may need to increase the maximum number of file descriptors.
...
| title | Example - Changing the maximum number of file descriptors on Linux |
|---|
...
| language | text |
|---|---|
| theme | Eclipse |
...
case the upgrade fails. |
| Info |
|---|
Use of Filebase persistenceWhen you have the platform property |
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. |
Place the *.tgz file from your release delivery into the staging directory.
Use a command line tool, go to the staging directory, and unpack the *.tgz file by running the following command:
Code Block $ tar xvzf <filename>.tgzA directory is then created in the staging directory, containing the software to be installed. For the purpose of these instructions, this directory is referred to as the release content directory.
Now copy the MZ license file into the release content directory.
| Info |
|---|
If you are upgrading from 8.3.x, you need a new license file. https://www.digitalroute.com/contact/contact-support/ on getting the MZ license file. |
| Code Block |
|---|
$ cp mz.license <release content directory> |
Enter the release content directory and prepare the
install.xmlfile by running the following command:
| Code Block |
|---|
$ cd <release content directory>
$ ./setup.sh prepare |
The *.mzp packages have now been extracted, and the install.xml has been extracted into the release content directory. The install.xml file will automatically be populated with information from your existing installation
...
.
...
...
mz.jdbc.user
...
mz.jdbc.password
...
mz.jdbc.url
...
install.db.jdbc.user
...
install.db.jdbc.password
...
install.sap.ssl.encrypt - If value is set to true then the following parameters must be manually set
install.sap.ssl.truststore
install.sap.ssl.truststorepassword
install.sap.ssl.hostnameincertificate
| Rw ui textbox macro | ||
|---|---|---|
| ||
| Note | ||
| Note | ||
Refer Updating the Installation Properties for Platform to know more about these properties and their default values. |
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Excerpt | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Properties for Oracle (to be removed) Properties for (to be removed) SAP HANA
|