Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 250.11
edited by Danniar Firdausy
on 2023/11/07 11:16
Change comment: There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/02/14 14:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -208 - Controlled State
1 +192 - Small Step
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -2,71 +2,64 @@
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. This overview covers a visibility towards the statistics for Retrieve Latency, Cache Size, Successful and Failed Retrieves. 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!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
6 6  
7 -{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
7 +== **Start/Stop Flows** ~*~* ==
8 8  
9 -== **State Generation~*~*** ==
9 +{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
10 10  
11 -//__New Page__//
12 -The following page has been added:
13 -* State generation statistics: Contains the statistics for state generation implementation in your model. This page can be found under Manage->Monitoring, right under the Topic statistics navigation menu. This page provides you with graphs that explains the Retrieve Latency, Cache Size, Successful and Failed Retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that has the add-on license for state generation.
11 +To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
14 14  
15 -{{info}}The graphs are configured with the same behaviour as graphs in the other statistics pages, meaning that you can also change the time range, zoom in zoom out to the time frame, etc.{{/info}}
13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
16 16  
17 -== **Feedback Items** ==
15 +After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
18 18  
19 -//__Improved Information on Removing a Release Version__//
20 -Users are now informed with a more comprehensive information of why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) is failed. Users are now informed in which environment(s) that runs in which runtime(s) that the release version under deletion is still running.
17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
21 21  
22 -//__Wider and Expandable Fields for XPath Expressions__//
23 -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.
19 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
24 24  
25 -//__Old Images Cleanup Mechanism__//
26 -We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz to take resources of the customer’s machine due to the unattended old images.
21 +== **Manage overview Event Streaming** ~*~* ==
27 27  
28 -//__Consistent Toggle Switches__//
29 -We are now implementing eMagiz Design System module in our platform and, in this release, we have updated all instances of the toggle switch to have a more consistent performance and look & feel throughout the platform.
23 +To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
30 30  
31 -//__Search Phrase__//
32 -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 user can search for entries with distances of 2 or incomplete search phrase (e.g., “startin engine” to look for “starting servlet engine”).
33 -
34 -//__Improved Image Building Performance__//
35 -We have implemented an improvement on the preparing step of the release at the begining of the deployment, which leads to a faster deployment process.
36 -
37 -//__Default "errorChannel" on Gen3 Migration__//
38 -During a migration of a model to Gen3, we have introduced a check now for flows that did not have custom error handling to be set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
39 39  
40 -There are cases where flows do not have a custom error handling. In this release, we During Gen3 Migration of a model.
41 -
42 -== **Bug Fixes** ==
27 +== **Feedback items ** ==
43 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 instead are deployed. This problem was caused by auto-healing that triggered during a new deployment.
29 +We have also solved other feedback items besides the flow designer's critical updates.
46 46  
47 -//__Log Messages in Gen3 Models__//
48 -We have implemented an improvement in our infra components that is intended to reduce the occurance of log messages failed to be sent in Gen3 models.
49 -
50 -//__Random Stuck in Deployment Plan Execution__//
51 -We addressed an issue where the execution of deployment plan would occasionally become stuck or halted unexpectedly.
31 +//__Topic configuration calculation__//
32 +With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
52 52  
34 +//__Make preparation step in deployment plan visible__//
35 +For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
36 +
37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
38 +
39 +//__3rd generation runtime debugger feedback__//
40 +We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
41 +
42 +//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43 +As of now you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
44 +
45 +//__User Management synchronization now happens in one step__//
46 +With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
47 +
53 53  == **Fancy Forum Answers** ==
54 54  
55 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:
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 dissapear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]]
59 -* [[Keystore not valid in runtime generation 3>>https://my.emagiz.com/p/question/172825635703261540||target="blank"]]
60 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
52 +* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53 +* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54 +* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
61 61  
62 -
63 63  == **Key takeaways** ==
64 64  
65 -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:
58 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
66 66  
67 67  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
68 68  * If you have feedback or ideas for us, talk to the Platypus
69 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
70 70  * Clear your browser cache (Ctrl + Shift + Del)
71 71  * Check out the release notes [here]
72 72  * Start thinking about how the license tracker can aid your development
... ... @@ -79,6 +79,6 @@
79 79  {{info}}
80 80  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
81 81  
82 -~*~* Indicates a next-generation-architecture only feature.
75 +~*~* Indicates a GEN3-only feature.
83 83  {{/info}})))((({{toc/}}))){{/container}}
84 84  {{/container}}