Skip to Content

Changes for page 208 - Controlled State

Last modified by CarlijnKokkeler on 2024/04/18 13:10
From version 262.1
edited by dfirdausy
on 2023/11/08 13:37
Change comment: There is no comment for this version
To version 17.1
edited by eMagiz
on 2022/10/13 09:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -208 - Controlled State
1 +185 - Get ready
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.eMagiz
Content
... ... @@ -2,68 +2,50 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have done much work to improve the functionality of our state-generation solution so that you can have a better overview of its implementation in your environment. Next to the monitoring for the state generation implementation in your model, several feedback items revolving around user interfacing components in our platform that can improve the user experience are also released. Lastly, some performance improvements and bug fixes have also been implemented.
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 -{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
7 +==**Audit trail User Management**==
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 +
10 +[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
8 8  
9 -== **State Generation - Manage overview** ==
10 -
11 -The following page has been added:
12 -* State generation statistics: Contains the statistics for state generation implementation in your model. The navigation to this page can be found under Manage->Monitoring page. This page provides you with graphs that explain the retrieve latency, cache size, and successful and failed retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that have the add-on license for state generation.
13 -
14 -[[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
15 -
16 -== **Feedback Items** ==
17 -
18 -//__Improved information on removing a release version__//
19 -Users are now informed with more comprehensive information about why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) fails. Users are now informed in which environment(s) and in which runtime(s) that the release version under deletion is still running.
20 -
21 -//__Wider and expandable fields for XPath expressions__//
22 -Input fields for XPath expressions located in the Create phase are now made wider and also capable of expanding when the expression registered by the user is too long.
23 -
24 -//__Old images cleanup mechanism__//
25 -We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz from taking resources from the customer’s machine due to the unattended old images.
26 -
27 -//__Consistent toggle switches__//
28 -In this release, we have updated all instances of the toggle switch to have a more consistent performance and look & feel throughout the platform.
29 -
30 -//__Consistent triggers naming__//
31 -We noticed that Trigger types have a different name throughout the portal. Therefore, in this release, on the Manage - Alerting page, we have renamed the "Source" column to "Source trigger" so that we have a consistent naming.
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 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.
32 32  
33 -//__Search phrase__//
34 -We are now enabling users to search for log entries and error messages based on phrases containing two or more words, instead of only one word or the full sentence. This also means that the user can search for entries with distances of 2 or incomplete search phrases (e.g., “startin engine” to look for “starting servlet engine”).
15 +* 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).
16 +* 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"]].
17 +* 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)
18 +* 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.
19 +* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
35 35  
36 -//__Improved image building performance__//
37 -We have implemented an improvement on the preparation step of the release at the beginning of the deployment, which leads to a faster deployment process.
38 38  
39 -//__Default "errorChannel" on next-generation architecture migration__//
40 -During a migration of a model to the next-generation architecture, we have introduced a check now for flows that did not have custom error handling to set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
22 +=== **Improvements** ===
41 41  
42 -== **Bug Fixes** ==
43 -
44 -//__Incorrect deployed containers__//
45 -A fix has been implemented to address the issue where older containers were deployed while it was shown that the new ones were deployed. This problem was caused by auto-healing that was triggered during a new deployment.
46 -
47 -//__Log messages in next-generation architecture models__//
48 -We have implemented an improvement in our infra components that is intended to reduce the occurrence of log messages failing to be sent in the next-generation architecture models.
49 -
50 -//__Random stuck in deployment plan execution__//
51 -We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly.
52 -
24 +* Performance Deployment plan
25 +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.
26 +
27 +* Flow Designer updates
28 +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.
29 +
30 +[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
31 +
32 +* Store
33 +We have fixed several smaller Store import issues to improve the user experience.
34 +
53 53  == **Fancy Forum Answers** ==
54 54  
55 -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:
37 +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:
56 56  
57 -* [[(Very) large messages via eMagiz>>https://my.emagiz.com/p/question/172825635703645419||target="blank"]]
58 -* [[Existing integration sends message to onramp but they disappear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]]
39 +* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
40 +* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
59 59  
60 60  == **Key takeaways** ==
61 61  
62 -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:
44 +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:
63 63  
64 64  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 -* 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.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 68  * Check out the release notes [here]
69 69  * Start thinking about how the license tracker can aid your development
... ... @@ -70,12 +70,13 @@
70 70  * Start thinking about major, minor, and patch
71 71  * Upgrade to the latest build number
72 72  * Keep making great integrations
55 +* Check out the new documentation portal.
73 73  
74 74  Let's stay in touch and till next time!
75 75  
76 76  {{info}}
77 -~* 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 +~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  
79 -~*~* Indicates a next-generation-architecture only feature.
62 +~*~* Indicates a GEN3-only feature.
80 80  {{/info}})))((({{toc/}}))){{/container}}
81 81  {{/container}}