Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+210 - Deployment Delights

Author

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

Content

...	...	@@ -1,55 +1,69 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
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 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	+**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
6	6
7		-== **3rd generation improvements and bug fixes** ==
	8	+== **Alerts** ==
8	8
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	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
11	11
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	+//__Missing metrics alert__//
	14	+We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
13	13
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	+== **Feedback Items** ==
16	16
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.
	18	+//__Improved release build process__//
	19	+When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
19	19
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.
	21	+//__Container version overview__//
	22	+Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
22	22
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	+[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
25	25
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	+//_Improved deployment process_//
	27	+The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
28	28
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	+//__Rebuilding of images__//
	30	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
30	30
31		-== **Feedback items ** ==
	32	+== **Bug Fixes** ==
32	32
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.
	34	+//__Runtime metrics processing__//
	35	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
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.
	37	+//__Deployment plan__//
	38	+We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
38	38
	40	+//__View all store items__//
	41	+An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
	42	+
	43	+//__Out of memory behavior__//
	44	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
	45	+
	46	+//__Max fetch size__//
	47	+In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
	48	+
39	39	== **Fancy Forum Answers** ==
40	40
41	41	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:
42	42
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"]]
	53	+* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
	54	+* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
	55	+* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
	56	+* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
	57	+* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
45	45
	59	+
46	46	== **Key takeaways** ==
47	47
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:
	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:
49	49
50	50	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
51	51	* If you have feedback or ideas for us, talk to the Platypus
52		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	66	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53	53	* Clear your browser cache (Ctrl + Shift + Del)
54	54	* Check out the release notes [here]
55	55	* Start thinking about how the license tracker can aid your development
...	...	@@ -62,6 +62,12 @@
62	62	{{info}}
63	63	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64	64
65		-~*~* Indicates a GEN3-only feature.
66		-{{/info}})))((({{toc/}}))){{/container}}
	79	+~*~* Indicates a next-generation-architecture only feature.
	80	+{{/info}}
	81	+)))
	82	+
	83	+(((
	84	+{{toc/}}
	85	+)))
67	67	{{/container}}
	87	+{{/container}}