Changes for page 216 - Hack Heaven

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -2,34 +2,20 @@
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** ==
9	9
10		-As eMagiz, we continuously validate our best practices configuration on security to the industry-wide standards in the fields of security to uphold our reputation as a reliable and secure integration platform. As a result of our latest evaluation, we decided to follow the industry-wide standard to **not** support the following TLS versions anymore in our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture for outgoing connections from eMagiz to external systems as of April 11th, 2024.
	10	+Placeholder for info from Bas
11	11
12		-* TLSv1.0
13		-* TLSv1.1
14		-
15	15	{{info}}Text{{/info}}
16	16
17	17	== **Announcement - Spring 6** ==
18	18
19		-We will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture in our release that will be released on April 11th, 2024. 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
20	20
21		-{{warning}}
22		-* 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.
23		-* To help you identify which flow versions are essential here, you can consider all flows that contain any of the following components:
24		-** Simple job launcher (data pipelines)
25		-** Job explorer (data pipelines)
26		-** HTTP components message sender (support object)
27		-** Web service outbound gateway (with a 'message sender' attribute specified)
28		-** SFTP session factory (support object)
29		-** API gateways with OAuth2 as security mechanism.
30		-* 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.
31		-** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. [[These release notes >>https://groovy-lang.org/releasenotes/groovy-4.0.html||target="blank"]] will specify the changes in more detail.
32		-* 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}}
33	33
34	34	== **Infra flow selection** ==
35	35