Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01

From version 443.1
edited by Carlijn Kokkeler
on 2024/04/08 12:51
Change comment: There is no comment for this version
To version 259.1
edited by Carlijn Kokkeler
on 2023/11/21 12:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +209 - Max Verstappen
Content
... ... @@ -3,44 +3,69 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
7 7  
8 +{{warning}}
9 +Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10 +{{/warning}}
8 8  
9 -== **Spring 6 Migration** ==
10 -As announced in our previous release blogs, 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, which is this release.
12 +== **Quicker Deployment Plan** ==
11 11  
12 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
13 -* JDBC BoneCP data source
14 -* SSL web service message sender
15 -* Web service outbound gateway
16 -* SFTP session factory
17 -* HTTP components message sender
18 -* Job manager
19 -* Credentials
20 -* Simple job launcher
21 -* Default SFTP session factory
14 +We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deployment plan will be finished much quicker now!
22 22  
23 -Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
16 +== **Next Generation Architecture Default** ==
24 24  
25 -In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
18 +With this release, the next generation architecture will become the default. New models will use this generation as default.
26 26  
27 -This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]].
20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
28 28  
22 +== **Cloud Template R11 Docker - Single Lane** ==
23 +
24 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
25 +
26 +== **Cloud Template R13 Docker - Double Lane** ==
27 +
28 +This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
29 +
29 29  == **Feedback Items** ==
30 -//__Event streaming logging__//
31 -* Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
32 32  
33 -//__Root Cloud__//
34 -Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
32 +//__Unused properties overview__//
33 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
35 35  
35 +* Not used by any runtime that is in the Create phase release.
36 +* Not required by a flow that is in the Create phase release.
37 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
38 +
39 +//__Queue explorer milliseconds__//
40 +The queue browser now displays milliseconds in the timestamps.
41 +
42 +//__Unused images__//
43 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
44 +
45 +//__Carwash logging__//
46 +A new logging feature enabling us to make better choices in encryption standards will be released.
47 +
48 +//__Static alerts queue consumers__//
49 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
50 +
51 +== **Bug Fixes** ==
52 +
53 +//__Flow Designer connection line__//
54 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
55 +
56 +//__Portal for migrated models__//
57 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
58 +
59 +//__Error channel inbounds__//
60 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
61 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
39 39  
40 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
41 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
66 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
42 42  
43 -== **Key Takeaways** ==
68 +== **Key takeaways** ==
44 44  
45 45  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
46 46  
... ... @@ -51,6 +51,7 @@
51 51  * Check out the release notes [here]
52 52  * Start thinking about how the license tracker can aid your development
53 53  * Start thinking about major, minor, and patch
79 +* Upgrade to the latest build number
54 54  * Keep making great integrations
55 55  
56 56  Let's stay in touch and till next time!
... ... @@ -58,6 +58,7 @@
58 58  {{info}}
59 59  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60 60  
87 +~*~* Indicates a next-generation-architecture only feature.
61 61  {{/info}}
62 62  )))
63 63