Skip to Content

Changes for page V341

Last modified by Erik Bakker on 2025/11/19 20:04
From version 8.1
edited by CarlijnKokkeler
on 2024/02/12 14:35
Change comment: There is no comment for this version
To version 47.1
edited by Erik Bakker
on 2025/11/19 20:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V2.1.0 - Reverted
1 +V341
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,20 +1,32 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}(((
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 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"]].
4 +{{info}}This image will be available for all users. If you notice any changed behavior that you believe is caused by this new image, we encourage you to notify us.{{/info}}
5 5  
6 -=====New features=====
6 +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"]].
7 7  
8 -New components to support a failover setup:
8 +====New features====
9 9  
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
10 +* Added support for automated configuration of API gateway containers, effectively making the gateway infra flow redundant about the security-related support objects. This feature will be rolled out with the introduction of Multiple Authentication Methods for API gateways.
11 +
12 +====Minor changes===
16 16  
17 -Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”.
14 +* Manage/Error Messages: Increased the maximum amount of displayed error message headers from 40 to 60.
15 +* For current generation models, the ‘Ssl web service message sender’ support object can now be configured without Truststore, which will make it fall back on the Java default Truststore. If no self-signed certificates are used, we recommend to remove previously configured truststores.
16 +** For legacy models, the Truststore path is still required, but the helptext has been updated to show the recommended configuration.
18 18  
18 +====Bug fixes====
19 +
20 +* Updated libraries below to implement a bugfix where, for some SFTP servers, storing files with mode ‘append’ would result in using an ‘insert’ mode instead. For example, sending the content 123456 to a file that currently has content abcdefghi would result in output 123456ghi instead of abcdefghi123456
21 +** Updated library org.apache.sshd:sshd-common from 2.14.0 to 2.16.0
22 +** Updated library org.apache.sshd:sshd-core from 2.14.0 to 2.16.0
23 +** Updated library org.apache.sshd:sshd-sftp from 2.14.0 to 2.16.0
24 +* When using a web service outbound gateway with a custom SSL web service message sender, the web senders' attributes, such as credentials and timeouts, were not applied to outgoing requests.
25 +* Upgraded our Java runtime from 17 to 21.
26 +** Resolved unnecessary warning logging during startup.
27 +* Support for configuring ‘NT Credentials’ in the ‘HTTP Components message sender' support object was unintentionally removed. This support has been added back, but the functionality is now marked as deprecated and will be removed in a future version.
28 +
29 +{{warning}}NT Credentials has been deprecated as credentials type for the ‘HTTP Components message sender’ support object, and is expected to be removed in the near future. We encourage you to change to a different authentication mechanism if possible.{{/warning}}
30 +
19 19  )))((({{toc/}}))){{/container}}
20 20  {{/container}}