Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 415.1
edited by Erik Bakker
on 2024/03/11 15:13
Change comment: There is no comment for this version
To version 416.1
edited by Erik Bakker
on 2024/03/11 15:15
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,10 +13,16 @@
13 13  
14 14  == **Announcement - Spring 6** ==
15 15  
16 -Placeholder for info from Jelle
16 +In the next release, we expect to release a major version of our current runtime base image. 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.
17 17  
18 -{{warning}}Text{{/warning}}
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 changes. 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 especially important here, you can consider all flows that contain any of the following components: Simple job launcher (data pipelines), Job explorer (data pipelines), HTTP components message sender (support object), Web service outbound gateway (with a 'message sender' attribute specified), SFTP session factory (support object), API gateways with OAuth2 as security mechanism.
21 +* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java version changes and the Spring version changes, 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.
22 +* In addition, the groovy version used has been moved from version 3.0.19 to 4.0.18. These changes may affect your scripts as well. These release notes outline the major changes
23 +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}}
19 19  
25 +
20 20  == **Infra flow selection** ==
21 21  
22 22  This release will include a significant update to our release functionality, which allows you to configure your release. Presently, eMagiz will allow you to see changes on the infra-flow level visually.