Wiki source code of V2.1.0 - Reverted
Version 8.1 by Carlijn Kokkeler on 2024/02/12 14:35
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}}((( | ||
| |
7.1 | 3 | |
| |
1.1 | 4 | These are the release notes for this runtime image. Once a runtime image is released, every new release will utilize this runtime image as base for creating runtime images for docker. For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. |
| 5 | |||
| |
3.1 | 6 | =====New features===== |
| |
1.1 | 7 | |
| |
3.1 | 8 | New components to support a failover setup: |
| |
1.1 | 9 | |
| |
4.1 | 10 | * Clustered lock registry: obtain a lock that can be shared over different containers |
| |
3.1 | 11 | * Leader initiator: Used to automatically start and stop roles based on whether they can obtain a cluster-wide lock |
| 12 | * New & extended operations for controlling integration components | ||
| 13 | ** New: Start & stop all components in a specific role, so you can start and stop multiple components at the same time | ||
| 14 | ** New: List all roles and whether they support leadership | ||
| 15 | ** Extended: List flow components now also shows whether a component is configured to be in a role | ||
| 16 | |||
| 17 | Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”. | ||
| 18 | |||
| |
1.1 | 19 | )))((({{toc/}}))){{/container}} |
| 20 | {{/container}} |