Changes for page 198 - Great Migration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+198 - Great Migration

Content

...	...	@@ -2,117 +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!** It has been a while since our last deployment on the 9th of December. As a result, we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. This release is characterized by the significant steps we took to release several major features on our 3rd generation runtime, including the queue browser and message redelivery functionality.
	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		-== **Queue Browser** ~*~* ==
	7	+== **3rd generation improvements and bug fixes** ==
8	8
9		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
	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		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called the "Queue browser." You can access this functionality via the "Explore" menu in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
	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}}
12	12
13		-To do so, we offer two options within this functionality. First, we have the Explore function, and we have the Wiretap function. When selecting a queue and opting for the Explore option, you get a live view of the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
	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.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	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.
16	16
17		-After selecting the queue and choosing the option, eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option), or that passed the queue since the moment you activate the option (Wiretap option). For each message, you have various options at your disposal.
	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.
18	18
19		-* Delete the message from the queue (Explore option)
20		- ** This means throwing away live data, which can be helpful in a test or acceptance environment where you inadvertently put many messages on a queue.
21		-* Clear message from the wiretap queue (Wiretap option)
22		- ** Once you are done with the analysis of a specific message in the wiretap functionality, you can clear it from the overview so it does not clutter the view anymore
23		-* Refresh messages list (both options)
24		- ** By pressing this button, you can refresh the list of messages displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25		-* Save as test message
26		- ** By pressing this button, you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so, we link the message to your model so you can still use it in the flow testing functionality.
27		-* Download
28		- ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
	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.
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	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.
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	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}}
33	33
34		-== **Message Redelivery ** ~*~* ==
35		-
36		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment.{{/warning}}
37		-
38		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
39		-
40		-As with our current offering, we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience, we have placed this functionality under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
41		-
42		-As in the current functionality, you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that, you can still see the linked error message as you could before.
43		-
44		-On top of that, we have added some additional functionality.
45		-
46		-* Search option
47		- ** Original queue name
48		- ** Original message ID (which can be found as a header called jms_messageid in the error message view)
49		-* Save as test message
50		- ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
51		-* Download
52		- ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
53		-
54		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
55		-
56		-== **3rd generation runtime bolstering** ==
57		-
58		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
59		-
60		-//__Define memory settings for on-premise runtimes from Deploy Architecture__//
61		-With this release, you can now define the memory settings (and, therefore, the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise.
62		-
63		-//__Empty runtime feedback when deploying a release (or setting the release as active)__//
64		-To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
65		-
66		-//__Auto-fill namespaces for SOAP hosted webservices__//
67		-Based on your configuration in Design, eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
68		-
69		-//__Updated H2 database setting__//
70		-As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
71		-
72		-{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
73		-
74		-//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
75		-As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime.
76		-
77		-//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
78		-With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
79		-
80		-//__Performance improvement creating a release__//
81		-With this release, we have improved the performance of creating a release.
82		-
83	83	== **Feedback items ** ==
84	84
85		-We have also solved other feedback items besides the flow designer's critical updates.
	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.
86	86
87		-//__Sensitive information stored in properties is masked __//
88		-We have made how we display sensitive information across the portal similar for various parts of the portal.
	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.
89	89
90		-//__Importing "Private" store content to which you do not have access__//
91		-We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
92		-
93		-
94		-== **Bug fixes ** ==
95		-
96		-//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
97		-We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
98		-
99		-//__Synchronization of Event Streaming topic states__//
100		-We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
101		-
102		-//__Copy and paste default support objects__//
103		-With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
104		-
105		-//__Fix editability of properties when importing store items__//
106		-With this release, you can once again change property names upon importing a store item.
107		-
108	108	== **Fancy Forum Answers** ==
109	109
110	110	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:
111	111
112		-* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
113		-* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
114		-* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
115		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||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"]]
116	116
117	117	== **Key takeaways** ==
118	118