Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+205 - World Explorers

Content

...	...	@@ -2,84 +2,67 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
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.
	5	+**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
6	6
7		-== **3rd generation runtime bolstering** ==
	7	+== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
8	8
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.
	9	+As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
10	10
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.
	11	+== **Feedback Items** ==
13	13
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.
	13	+//__Improved Validation when migrating to the next-generation architecture__//
	14	+To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
16	16
17		-//__Autogenerated exits can be deployed at once__//
18		-This release has fixed a bug that prevented you from deploying an exit flow correctly.
	16	+{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
19	19
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.
	18	+//__Improved HTTP Statistics__//
	19	+To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
22	22
23		-//__Failing runtimes won't be restarted indefinitely anymore__//
24		-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.
	21	+//__"Topic Full" alert restriction changed__//
	22	+With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
25	25
26		-== **Exportable Release Audit** ~* ==
	24	+//__Improved performance Manage Dashboards__//
	25	+We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
27	27
28		-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.
	27	+//__Show values on the runtime level in Deploy Architecture__//
	28	+We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
29	29
30		-[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
	30	+{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
	31	+* JMS - The number of queues in the active release.
	32	+* Messaging Container - The number of messaging integrations in the active release.
	33	+* Messaging Connector - The number of messaging integrations related to this system in the active release.
	34	+* API Gateway Container - The number of operations in the active release.
	35	+* Event Streaming Container - The number of event processors in the active release.
31	31
32		-{{warning}}Note that the following restrictions apply when exporting an audit document:
33		- * Works **only** for releases that are promoted and made active on **Production**
34		- * You will **only** see changes made during the **current** calendar year
35		- * On the first of April all objects of the **last** calendar year will be **removed**.
36		- ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
	37	+There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
37	37
38		-== **Feedback items ** ==
	39	+== **Bug Fixes** ==
39	39
40		-We have also solved other feedback items besides the flow designer's critical updates.
	41	+//__Improved information Queue Statistics__//
	42	+Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
41	41
42		-//__Improved naming convention on Store related pages__//
43		-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.
	44	+//__Gain the ability again to configure certificates in Deploy Architecture again__//
	45	+In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
44	44
45		-//__Press "Enter" to search on multiple pages__//
46		-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.
	47	+//__Ensure that differing container configurations deploy the correct configuration__//
	48	+When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
47	47
48		-* Deploy → Deployment Plan
49		-* Deploy → Properties → History
50		-* Deploy → User Management → Roles
51		-* Manage → Error Messages → Error Messages
52		-* Manage → Error Messages → Flows with Error Messages
53		-* Manage → Error Messages → Exceptions of Error Messages
54		-* Manage → Log Entries
55		-* Manage → Alerts
56		-* Manage → Triggers
57		-* Manage → Tags – Cant find (only Gen2)
58		-* Manage → Notifications
59		-* Manage → Notification Settings
60		-* Manage → Data Usage → History
61		-* Manage → Code mappings → All tabs
	50	+//__Remove queurying options in Manage__//
	51	+To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
62	62
63		-== **Bug fixes ** ==
64		-
65		-//__Loading problems of Deployment plan execution overview__//
66		-We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
67		-
68	68	== **Fancy Forum Answers** ==
69	69
70	70	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:
71	71
72		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
73		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
74		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	57	+* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
75	75
76	76	== **Key takeaways** ==
77	77
78		-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:
	61	+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:
79	79
80	80	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
81	81	* If you have feedback or ideas for us, talk to the Platypus
82		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	65	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83	83	* Clear your browser cache (Ctrl + Shift + Del)
84	84	* Check out the release notes [here]
85	85	* Start thinking about how the license tracker can aid your development
...	...	@@ -92,6 +92,6 @@
92	92	{{info}}
93	93	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94	94
95		-~*~* Indicates a GEN3-only feature.
	78	+~*~* Indicates a next-generation-architecture only feature.
96	96	{{/info}})))((({{toc/}}))){{/container}}
97	97	{{/container}}