Page Comparison

...

1. Shut down the Platform prior to the downgrade:

   Code Block
   language text theme Eclipse
   $ mzsh shutdown platform

   
   

   Note
   title Note!
   If you are using SAP HANA as the Platform database, you will need to disable the TLS/SSL on the SAP HANA database before you downgrade your Platform. Refer to Downgrade 8.2 on the Release Documentation for the steps.

   
   

2. Downgrade the Platform Container by using the setup script setup.sh, that was extracted when unzipping the upgrade software.

   Code Block
   language text theme Eclipse
   $./setup.sh downgrade

   
   The setup script will automatically try to detect which version you want to downgrade from ,and which version you want to downgrade to.
   
   If the script does not succeed in detecting the versions, you will be prompted for the versions.
    

3. When the versions have been determined, you will be asked if you want to proceed. Enter yes to proceed.
   
   You will now be prompted for user name and password.
    

4. Enter user name and password, and the downgrade will start.

   Tip
   title Hint!
   You can also add the user name and password properties to the setup.sh script. Code Block language text theme Eclipse $ ./setup.sh downgrade -Dmz.username=mzadmin -Dmz.password=<password>

   When using the setup.sh downgrade command, three different log files will be created; generate<timestamp>.log, validate<timestamp>.log, and down- grade<timestamp>.log. By default, these log files will be placed in the same directory as setup.sh. If you want the log file to be placed in another directory, you can add the upgradelogdir property to the setup script.

   Info
   title Example - Downgrading the Platform
   Code Block language text theme Eclipse $ ./setup.sh downgrade -Dmz.upgradelogdir=<directory path>

   
   

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

   A successful downgrade command will print out "Version successfully changed from <new version> to <previous version>" at the end of the command output.

   In case the downgrade was unsuccessful, this will be indicated. Check the latest upgrade_<timestamp>.log file for further details in order to analyze the result and see what may have caused the problem.
    

5. If any of your configurations have been resaved in the upgraded system, the configurations from the old version that was exported in section 7.2 Preparations need to be imported.