Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 419.1
edited by Erik Bakker
on 2024/03/11 15:19
Change comment: There is no comment for this version
To version 415.1
edited by Erik Bakker
on 2024/03/11 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 -
5 +
6 6  **Hi there, eMagiz developers!** As part of our alignment week, we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that, we launch new functionality that makes it easier to transform to JSON, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions. But before we dive into all that has changed, we will publish several announcements via this release blog (and other channels) to prepare your model for upcoming major changes.
7 7  
8 8  == ** Announcement - TLS versions deprecated** ==
... ... @@ -13,20 +13,9 @@
13 13  
14 14  == **Announcement - Spring 6** ==
15 15  
16 -We expect to release a major version of our current runtime base image for all our clients running on the **current runtime** architecture in the next release. This image moves the eMagiz stack from Java 8 to Java 17 and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
16 +Placeholder for info from Jelle
17 17  
18 -{{warning}}
19 -* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changed. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting
20 -* To help you identify which flow versions are essential here, you can consider all flows that contain any of the following components:
21 -** Simple job launcher (data pipelines)
22 -** Job explorer (data pipelines)
23 -** HTTP components message sender (support object)
24 -** Web service outbound gateway (with a 'message sender' attribute specified)
25 -** SFTP session factory (support object)
26 -** API gateways with OAuth2 as security mechanism.
27 -* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java and Spring versions change, this may affect the availability of the libraries on the classpath and, therefore, the validity of import statements. You can already test the Groovy script using the flow testing functionality, as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
28 -** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. The release notes of the base image will specify the changes in more detail.
29 -* The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production. {{/warning}}
18 +{{warning}}Text{{/warning}}
30 30  
31 31  == **Infra flow selection** ==
32 32