This chapter describes the standard upgrade procedure. Standard upgrades must be performed stepwise, i e to the next consecutive main or minor version. This procedure should be used when it is required to minimize downtime during upgrade and to ensure that configurations, persisted data (in the file system or database), and system properties are properly migrated. If this is not required, and you only wish to migrate configuration data, you may perform the simplified upgrade procedure instead. For information about the simplified upgrade procedure, see 8. Simplified Upgrade Procedure.
The upgrade procedure consists of the following steps:
- Getting Started
- Preparations
- Disconnect ECSAs
- Shut down Execution
- Upgrade the Platform Container
- Upgrade the Execution Containers
- Desktop Reinstallation
- Post Upgrade
- Resume Workflow Execution
If you plan to upgrade several versions, repeat steps 2-9 for each version. Use the setup.sh script provided for each version during the upgrade.
| Note | ||
|---|---|---|
| ||
There may be changes to certain agents and functions in the new version. Before upgrading, you should take note of any changes or updates that may have happened to your components, as you may have to modify your configuration before it can work with the newer version. |
| Note | ||
|---|---|---|
| ||
If you use High Availability, it is advised that you deactivate the failover functionality in the HA cluster daemon. You must ensure that no HA activities can impede the upgrade procedure. |