Skip to Content

Changes for page V3.1.1

Last modified by Erik Bakker on 2024/07/16 15:10
From version 35.2
edited by Carlijn Kokkeler
on 2024/07/16 14:35
Change comment: Update document after refactoring.
To version 8.1
edited by Carlijn Kokkeler
on 2024/02/12 14:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V3.1.1
1 +V2.1.0 - Reverted
Content
... ... @@ -3,15 +3,18 @@
3 3  
4 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 5  
6 -=====Minor changes=====
6 +=====New features=====
7 7  
8 -* Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be reset (or updated) in order to also store the messages for 10 minutes instead of 5.
8 +New components to support a failover setup:
9 9  
10 -=====Bug fixes=====
10 +* Clustered lock registry: obtain a lock that can be shared over different containers
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
11 11  
12 -* Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP.
13 -* The SMB outbound gateway with the GET command did not work, this has been resolved.
14 -* In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue.
17 +Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”.
15 15  
16 16  )))((({{toc/}}))){{/container}}
17 17  {{/container}}