Skip to Content

Changes for page V341

Last modified by Erik Bakker on 2025/11/19 20:04
From version 45.1
edited by Erik Bakker
on 2025/10/21 10:52
Change comment: There is no comment for this version
To version 16.1
edited by CarlijnKokkeler
on 2024/04/08 11:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V3.4.0
1 +V3.0.0
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,27 +1,37 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}(((
3 3  
4 -{{warning}}This image will only be available for our flow testing image and for customers running on our Beta image. If you notice any changed behavior during flow testing that you believe is the cause, we encourage you to notify us.{{/warning}}
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 -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"]].
6 +=====Major changes=====
7 7  
8 -====New features====
8 +* Updated our Java runtime version from Java 8 (8u352-b08) to Java 17 (17.0.10_7).
9 +* Updated Spring boot version from 2.7 to 3.2:
10 +** Updated Spring Framework from 5 to 6
11 +** Updated Java EE 8 to Jakarta EE 10
12 +* SSL version support changes:
13 +** TLS version 1.1 is no longer supported. We have kept support for TLS version 1.1 for an extended time to support legacy systems, and feel it is appropriate to remove support as we see negligible traffic still using this TLS version.
14 +** TLS version 1.3 is now the default (was TLS version 1.2). TLS version 1.2 will remain supported.
15 +* OAuth2 authorization no longer supports the previously deprecated implicit grant type.
16 +* SOAP webservices: For webservices outbound gateways, the default hostname verifier was changed from browser compatible to strict. No major impact is expected here as the strict behavior is considered to be industry default. Only webservers that provide a server certificate with a wildcard may be affected (e.g. having a Common Name such as *.emagizcloud.com), and only if the endpoint that is being called is on a deeper level than the certificate (e.g. webservice.api.emagizcloud.com) AND the server certificate does not contain that endpoint (as a Subject Alternative Name).
17 +* Data pipelines: Spring has changed the database schema used for data pipelines operations. When the default H2 database is used for data pipelines, we automatically migrate your database schema to the new flavor. Note: this does block you from moving back to a previously activated release, unless the image is re-built.
18 +* JDBC Data source support: The BoneCP data source support object has been removed and replaced by the Hikari data source support object. eMagiz will generate a Hikari data source in every flow containing a BoneCP data source, after which you should verify the settings, replace the data source references and remove the BoneCP support object before deploying.
19 +* Several components have small changes in their configurations which require a new flow version to be included in your release. eMagiz will create new flow versions for these changes, which you need to manually include in your release. These affects any flow that has any of the following components:
20 +** Data pipelines:
21 +***‘simple job launcher’ → eMagiz will push a new flow version which replaces this with ‘task executor job launcher’
9 9  
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===
23 +‘job explorer’ → eMagiz will push a new flow version which adds a ‘data source’.
13 13  
14 -* Manage/Error Messages: Increased the maximum amount of displayed error message headers from 40 to 60.
25 +Http message sender: HttpComponentsMessageSender → eMagiz will replace this with HttpComponents5MessageSender
15 15  
16 -====Bug fixes====
27 +SOAP webservices: Web service outbound gateway → eMagiz will push a new version to keep the resulting code compatible. No functional changes
17 17  
18 -* 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
19 -** Updated library org.apache.sshd:sshd-common from 2.14.0 to 2.16.0
20 -** Updated library org.apache.sshd:sshd-core from 2.14.0 to 2.16.0
21 -** Updated library org.apache.sshd:sshd-sftp from 2.14.0 to 2.16.0
22 -* 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.
23 -* Upgraded our Java runtime from 17 to 21.
24 -** Enabled Java’s virtual threads, improving overall throughput and reducing overhead. This results in a minor change where the stack trace in error messages may no longer show the ‘… xx common frames omitted’ as part of the stack trace
29 +Credentials
25 25  
31 +SFTP session factory → eMagiz will push a new flow version to keep the resulting code compatible.
32 +
33 +Secured channels support object, used by API gateways with OAuth2 security, is removed → eMagiz will push a new flow version where this is migrated to the ‘HTTP security’ support object instead.
34 +=====Minor changes=====
35 +
26 26  )))((({{toc/}}))){{/container}}
27 27  {{/container}}