Changes for page 208 - Controlled State

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-208 - Controlled State
	1	+198 - Great Migration

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.dfirdausy
	1	+XWiki.ebakker

Content

...	...	@@ -2,65 +2,54 @@
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!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture as well as improved the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our own infrastructure to ensure that all data flowing via this infrastructure now more and more customers are migrating can be handled as good if not better as before.
6	6
7		-{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
	7	+== **3rd generation improvements and bug fixes** ==
8	8
9		-== **State Generation - Manage overview** ==
	9	+//__"Stop" action when running a hybrid situation is not causing issues anymore__//
	10	+Before, it could happen when running a double-lane setup in a hybrid situation (i.e karaf based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release that behavior is changed.
10	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.
	12	+{{info}}Note that this fix is part of a new runtime image for the karaf based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
13	13
14		-[[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
	14	+//__Removed certain dependencies between Deploy Architecture and Releases__//
	15	+In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release.
15	15
16		-== **Feedback Items** ==
	17	+//__Improved validation errors on invalid configuration of HTTP outbound components__//
	18	+This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
17	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	+//__Improved migration behavior__//
	21	+This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished.
20	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	+//__Improved auto-healing when running in a hybrid situation__//
	24	+In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
23	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	+//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
	27	+To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
26	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	+{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
29	29
30		-//__Search phrase__//
31		-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”).
32		-
33		-//__Improved image building performance__//
34		-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.
35		-
36		-//__Default "errorChannel" on next-generation architecture migration__//
37		-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.
38		-
39		-== **Bug Fixes** ==
	31	+== **Feedback items ** ==
40	40
41		-//__Incorrect deployed containers__//
42		-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.
	33	+//__Make sure the message format can be viewed without "Start editing"__//
	34	+With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
43	43
44		-//__Log messages in next-generation architecture models__//
45		-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.
	36	+//__Various styling improvements in the flow testing functionality__//
	37	+Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
46	46
47		-//__Random stuck in deployment plan execution__//
48		-We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly.
49		-
50	50	== **Fancy Forum Answers** ==
51	51
52	52	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:
53	53
54		-* [[(Very) large messages via eMagiz>>https://my.emagiz.com/p/question/172825635703645419||target="blank"]]
55		-* [[Existing integration sends message to onramp but they disappear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]]
	43	+* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
	44	+* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
56	56
57	57	== **Key takeaways** ==
58	58
59		-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:
	48	+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:
60	60
61	61	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
62	62	* If you have feedback or ideas for us, talk to the Platypus
63		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	52	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64	64	* Clear your browser cache (Ctrl + Shift + Del)
65	65	* Check out the release notes [here]
66	66	* Start thinking about how the license tracker can aid your development
...	...	@@ -73,6 +73,6 @@
73	73	{{info}}
74	74	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75	75
76		-~*~* Indicates a next-generation-architecture only feature.
	65	+~*~* Indicates a GEN3-only feature.
77	77	{{/info}})))((({{toc/}}))){{/container}}
78	78	{{/container}}