Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+188 - Close Encounters

Content

...	...	@@ -2,39 +2,74 @@
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 the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
	5	+**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6	6
7		-== **3rd generation improvements and bug fixes** ==
	7	+== **3rd generation runtime bolstering** ==
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.
	9	+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.
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}}
	11	+//__Migration of JMS backup configuration improved__//
	12	+With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
13	13
14		-//__Improved efficiency in deploying a release__//
15		-This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
	14	+//__Prechecks on Upgrade option made available for 3rd generation runtime__//
	15	+As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
16	16
17		-//__Removed specific dependencies between Deploy Architecture and Releases__//
18		-In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
	17	+//__Autogenerated exits can be deployed at once__//
	18	+This release has fixed a bug that prevented you from deploying an exit flow correctly.
19	19
20		-//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21		-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.
	20	+//__Code mapping functionality available on 3rd generation runtime__//
	21	+As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
22	22
23		-//__Improved migration behavior__//
24		-This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25		-A smoother migration of your JMS (and backup JMS) process.
26		-Shortening of names that otherwise would be too long, additional feedback given to the user.
27		-Feedback when the migration process is finished.
	23	+//__Improved the performance when activating a release__//
	24	+With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
28	28
29		-//__Additional checks when deploying__//
30		-This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
	26	+//__Failing runtimes won't be restarted indefinitely anymore__//
	27	+We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
31	31
	29	+== **Exportable Release Audit** ~* ==
	30	+
	31	+On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
	32	+
	33	+[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
	34	+
	35	+{{warning}}Note that the following restrictions apply when exporting an audit document:
	36	+ * Works **only** for releases that are promoted and made active on **Production**
	37	+ * You will **only** see changes made during the **current** calendar year
	38	+ * On the first of April all objects of the **last** calendar year will be **removed**.
	39	+ ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
	40	+
	41	+== **Feedback items ** ==
	42	+
	43	+We have also solved other feedback items besides the flow designer's critical updates.
	44	+
	45	+//__Improved naming convention on Store related pages__//
	46	+We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
	47	+
	48	+//__Press "Enter" to search on multiple pages__//
	49	+In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
	50	+
	51	+* Deploy → Deployment Plan
	52	+* Deploy → Properties → History
	53	+* Deploy → User Management → Roles
	54	+* Manage → Error Messages → Error Messages
	55	+* Manage → Error Messages → Flows with Error Messages
	56	+* Manage → Error Messages → Exceptions of Error Messages
	57	+* Manage → Log Entries
	58	+* Manage → Alerts
	59	+* Manage → Triggers
	60	+* Manage → Tags – Cant find (only Gen2)
	61	+* Manage → Notifications
	62	+* Manage → Notification Settings
	63	+* Manage → Data Usage → History
	64	+* Manage → Code mappings → All tabs
	65	+
32	32	== **Fancy Forum Answers** ==
33	33
34	34	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:
35	35
36		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	70	+* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
	71	+* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
	72	+* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
38	38
39	39	== **Key takeaways** ==
40	40