Upgrade Execution Container
This page explains how to upgrade the Execution Container using the Standard Upgrade Procedure. Before proceeding, ensure that you have reviewed all the "Pre-Upgrade" pages.
During the upgrade process, always use the default application user, mzadmin, along with the correct password when prompted.
Note!
Ensure that the install.type value is set to ec only when upgrading the Execution Container.
These properties should be configured according to the platform container setup. For more information, refer to Execution Container Properties.
Upgrading the Execution Container
1. Navigate to the Release Content Directory
Access the directory created during the extraction of the delivered *.tgz file in the Upgrade Preparation step.
2. Execute the Upgrade Command
Pre-upgrade validations are performed to verify the environment and configuration, ensuring a seamless upgrade experience. To perform validation without starting the upgrade, run the following command:
$ ./setup.sh upgrade -validate-onlyRun the following command to initiate the upgrade process.
$ ./setup.sh upgradeNote!
If the upgrade validation fails, there is no need to perform a rollback or restore, as the upgrade process has not yet begun.
If validation fails but you choose to proceed, you can run the following command.
$ ./setup.sh upgrade -skip-validate Caution!
You can choose to skip validation, but be aware that this bypasses checks for potential issues in your environment and configuration. If there are undetected problems, the upgrade may fail or cause unexpected behavior. Proceed with caution and ensure you have backups before continuing.
3. Monitor the Upgrade Progress
The ./setup.sh upgrade command generates a setup log file in the $MZ_HOME/log directory. To monitor the upgrade progress in real-time, use the following command in a separate window:
$ tail -f $MZ_HOME/log/setup-9.4.0.0.log4. Rollback in Case of Failure
If the upgrade is aborted and a rollback is necessary, see https://infozone.atlassian.net/wiki/spaces/MD92/pages/111805735.
Execution Container Post-Upgrade Steps
Restart ECs
$ mzsh restart <ec name>