Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 13.1
edited by eMagiz
on 2022/10/12 12:48
Change comment: There is no comment for this version
To version 440.1
edited by CarlijnKokkeler
on 2024/04/08 11:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get ready
1 +218 - Sprightly Spring
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,69 +1,67 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
6 +**Hi there, eMagiz developers!**
6 6  
7 -==**Store additions**==
8 -We have released several Store items that can be used in the Design Store and which include complete data models and transformations. See the list below of the components that have these.
9 -
10 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 3.png]]
11 11  
12 -==**Audit trail User Management**==
13 -Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
14 -
15 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
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.
16 16  
17 -==**Next Generation Monitoring & Alerting engine** (\*\*)==
18 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
19 -
20 -* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
21 -* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
22 -* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
23 -* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
24 -* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
25 -
26 -
27 -=== **Improvements** ===
28 -
29 -* Performance Deployment plan
30 -When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
31 -
32 -* Flow Designer updates
33 -We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
34 -
35 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
36 -
37 -* Store
38 -We have fixed several smaller Store import issues to improve the user experience.
39 -
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
22 +
23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
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"]].
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 image 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
28 +
29 +== **Feedback Items** ==
30 +
31 +== **Bug Fixes** ==
32 +//__Runtime overview improvements__//
33 +The runtime overview has been improved regarding checks on the runtime version.
34 +
40 40  == **Fancy Forum Answers** ==
41 41  
42 -As always, a gentle reminder to all 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:
37 +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:
43 43  
44 -* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
45 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
39 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
40 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
46 46  
47 -== **Key takeaways** ==
42 +== **Key Takeaways** ==
48 48  
49 -Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
44 +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:
50 50  
51 51  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
52 52  * If you have feedback or ideas for us, talk to the Platypus
53 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
48 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
54 54  * Clear your browser cache (Ctrl + Shift + Del)
55 55  * Check out the release notes [here]
56 56  * Start thinking about how the license tracker can aid your development
57 57  * Start thinking about major, minor, and patch
58 -* Upgrade to the latest build number
59 59  * Keep making great integrations
60 -* Check out the new documentation portal.
61 61  
62 62  Let's stay in touch and till next time!
63 63  
64 64  {{info}}
65 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
58 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66 66  
67 -~*~* Indicates a GEN3-only feature.
68 -{{/info}})))((({{toc/}}))){{/container}}
60 +{{/info}}
61 +)))
62 +
63 +(((
64 +{{toc/}}
65 +)))
69 69  {{/container}}
67 +{{/container}}