Changes for page 201 - Be Informed

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+198 - Great Migration

Content

...	...	@@ -2,43 +2,46 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
	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		-== **Next generation improvements and bug fixes** ==
	7	+== **3rd generation improvements and bug fixes** ==
8	8
9		-//__Enhanced overview of the HTTP Statistics__//
10		-As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
	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.
11	11
12		-//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13		-In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
	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}}
14	14
15		-{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	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.
16	16
17		-//__Forced congestion control__//
18		-To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
	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.
19	19
20		-//__Unused images are cleaned up__//
21		-This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
	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.
22	22
23		-== **Store Improvements** ==
	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.
24	24
25		-//__Improved importing behavior for specific use cases__//
26		-Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
	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.
27	27
28		-//__Fixed bug in creating a message mapping on top of an imported system message__//
29		-It is now possbile to create a message mapping to an imported system message from the store.
	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}}
30	30
31		-== **Event Streaming - Certificate Management** ==
	31	+== **Feedback items ** ==
32	32
33		-//__Expired certification notification__//
34		-As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	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.
35	35
	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.
	38	+
36	36	== **Fancy Forum Answers** ==
37	37
38	38	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:
39	39
40		-* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
41		-* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||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"]]
42	42
43	43	== **Key takeaways** ==
44	44