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. |
Excerpt | ||
---|---|---|
|
Excerpt | ||
---|---|---|
| ||
|
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
When using the
./setup.sh upgrade
command, setup log file will be generated in the$MZ_HOME/log
directory.
Tip |
---|
Hint! It may be a good idea to open a new command line window in order to keep track of the log files. |
Startup the platform.
Code Block $ mzsh startup platform
Start the pico for the User Interface.
Code Block $ 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. |
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.
|