Skip to Content

Changes for page V3.0.6

Last modified by Carlijn Kokkeler on 2024/07/17 14:39
From version 27.2
edited by Carlijn Kokkeler
on 2024/04/23 12:12
Change comment: Update document after refactoring.
To version 15.1
edited by Carlijn Kokkeler
on 2024/04/08 11:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V304
1 +V3.0.0
Content
... ... @@ -3,11 +3,46 @@
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 -=====Bug fixes=====
6 +=====Major changes=====
7 7  
8 -* The content-length header is now removed from all messages. With the latest Spring version, this HTTP header was no longer overridden when making HTTP (REST) requests. This could result in an error message ‘Too many bytes written’ or ‘Insufficient bytes written’ if the message contained the content-length header from a previous HTTP call. Behavior of the flow components has been changed so that it will never set the content-length header. **Note**: this means that manually setting the content-length header is no longer allowed. If your flows contain any component explicitly setting or overriding the content-length header, these should be removed.
9 -* SFTP Session Factories with a known-hosts file specified were not parsed properly.
10 -* In flows with a JMS inbound and a Kafka outbound, log messages at error level could occur due to jms_* headers on the message that could not be mapped to Kafka message headers. Since this message would be logged for every message that would be send, this log message has been disabled.
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 11  
12 +Updated Java EE 8 to Jakarta EE 10
13 +
14 +SSL version support changes:
15 +
16 +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.
17 +
18 +TLS version 1.3 is now the default (was TLS version 1.2). TLS version 1.2 will remain supported.
19 +
20 +OAuth2 authorization no longer supports the previously deprecated implicit grant type.
21 +
22 +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).
23 +
24 +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.
25 +
26 +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.
27 +
28 +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:
29 +
30 +Data pipelines:
31 +
32 +‘simple job launcher’ → eMagiz will push a new flow version which replaces this with ‘task executor job launcher’
33 +
34 +‘job explorer’ → eMagiz will push a new flow version which adds a ‘data source’.
35 +
36 +Http message sender: HttpComponentsMessageSender → eMagiz will replace this with HttpComponents5MessageSender
37 +
38 +SOAP webservices: Web service outbound gateway → eMagiz will push a new version to keep the resulting code compatible. No functional changes
39 +
40 +Credentials
41 +
42 +SFTP session factory → eMagiz will push a new flow version to keep the resulting code compatible.
43 +
44 +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.
45 +=====Minor changes=====
46 +
12 12  )))((({{toc/}}))){{/container}}
13 13  {{/container}}