Skip to Content

Changes for page V3.3.1

Last modified by Erik Bakker on 2025/04/22 14:07
From version 40.1
edited by Erik Bakker
on 2025/04/22 14:07
Change comment: There is no comment for this version
To version 4.1
edited by Carlijn Kokkeler
on 2024/01/15 11:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V3.3.1
1 +V2.1.0
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,12 +1,19 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}(((
3 +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"]].
3 3  
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 a base for creating runtime images for docker. For more information, 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 +=====New features=====
5 5  
6 -====Bug fixes====
7 +New components to support a failover setup:
7 7  
8 -* Support for the ‘NTCredentials’ authentication method in a custom HttpComponentsMessageSender support object has been reintroduced.
9 -* In some edge cases, log messages produced with the Logging channel adapter component did not reach the Manage phase. This issue is now resolved.
9 +* Clustered lock registry: obtain a lock that can be shared over different containers
10 +* Leader initiator: Used to automatically start and stop roles based on whether they can obtain a cluster-wide lock
11 +* New & extended operations for controlling integration components
12 +** New: Start & stop all components in a specific role, so you can start and stop multiple components at the same time
13 +** New: List all roles and whether they support leadership
14 +** Extended: List flow components now also shows whether a component is configured to be in a role
10 10  
16 +Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”.
17 +
11 11  )))((({{toc/}}))){{/container}}
12 12  {{/container}}