Skip to Content

Changes for page 185 - Get ready

Last modified by Carlijn Kokkeler on 2024/04/18 13:22
From version 4.1
edited by eMagiz
on 2022/10/12 11:03
Change comment: There is no comment for this version
To version 7.1
edited by eMagiz
on 2022/10/12 11:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,14 +4,26 @@
4 4  
5 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 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 +
7 7  ==**Audit trail User Management**==
8 8  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.
9 9  
10 -[[image:Main.Images.Release Blog.WebHome@185 - Releaseblog 1.png]]
15 +[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
11 11  
12 12  ==**Next Generation Monitoring & Alerting engine**==
13 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now used 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. 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). We have already 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"]]
18 +In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now used 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.
14 14  
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 +
15 15  === **Improvements** ===
16 16  
17 17  * Performance Deployment plan
... ... @@ -20,8 +20,11 @@
20 20  * Flow Designer updates
21 21  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.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@185 - Releaseblog 2.png]]
35 +[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
24 24  
37 +* Store
38 +We have fixed several smaller Store import issues to improve the user experience.
39 +
25 25  == **Fancy Forum Answers** ==
26 26  
27 27  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: