...
| Note |
|---|
Before starting the upgrade, please ensure that all Desktop clients have been logged out. If you want to see which Desktops that are connected, you can use the following command: | Code Block |
|---|
| $ mzsh mzadmin/<password> pico -view |
|
| Excerpt |
|---|
| Note |
|---|
Note| Panel |
|---|
| panelIconId | atlassian-warning |
|---|
| panelIcon | :warning: |
|---|
| bgColor | #FFBDAD |
|---|
| When upgrading to  9.x, the install.admin.password MUST must be set according to your current admin password before proceeding with the ./setup.sh upgrade step. |
|
| Excerpt |
|---|
| | Note |
|---|
Note |
| Panel |
|---|
| panelIconId | atlassian-warning |
|---|
| panelIcon | :warning: |
|---|
| bgColor | #FFBDAD |
|---|
| If the existing installation has additional JVM argument configured before, you need to check if there are obsoleted in Java 17. You MUST must remove them if there are obsoleted. Refers to Managing Picos with Topo for JVM Arguments configuration. |
|
...
A successful upgrade may print out "The following things may require your manual attention" at the end of the command output, followed by a list of things that may need manual attention. In case the upgrade was unsuccessful, this will be indicated. Check the latest setup log for further details in order to analyze the result and see what may have caused the problem. If it is needed, a downgrade can be performed. For information about how to perform a downgrade, see Simplified Downgrade Procedure.
| Note |
|---|
If you are upgrading from 8.x and the upgrade fails, you may want to perform a rollback using the old MZ_HOME backup. |
| 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 |
|---|
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. |
...