Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 341.1
edited by Carlijn Kokkeler
on 2024/01/15 14:44
Change comment: There is no comment for this version
To version 150.1
edited by Erik Bakker
on 2023/08/29 10:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +204 - Found It
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,39 +1,36 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release...
5 +**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
7 7  
8 -== **Cloud Template R20 - Double Lane** ==
7 +== **Feedback Items** ==
9 9  
10 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]].
9 +//__Improved check on nested property placeholders__//
10 +To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
11 11  
12 -== **Cloud Template R27 - Single Lane** ==
12 +//__Removed outdated properties when deploying on the new generation architecture stack__//
13 +We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate.
13 13  
14 -This release introduces a new non-service affecting cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R27 - Single lane.WebHome||target="blank"]].
15 +{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
15 15  
16 -== **Feedback Items** ==
17 +//__Improved performance Manage Dashboards__//
18 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
17 17  
18 -//__Failover setup__//
19 -New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
20 -
21 -
22 22  == **Bug Fixes** ==
23 23  
24 -//__Message merging tool__//
25 -The message merging tool has been fixed to allow merging a store item message model into your own message models. In some rare cases your CDM message may be broken due to incorrect data. In those cases, the message mapping and message merge functionalities will be broken as well. If this broken data is detected when navigating to CDM-message-related pages, you will be able to clean your CDM message.
22 +//__Errors with long stack traces or long message histories will now also show in eMagiz__//
23 +We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
26 26  
27 -//__Catalog topic definitions__//
28 -It is now possible to generate a JSON Example of a topic whose schema has nested elements. Before, an error would occur when trying to generate a JSON example in this case.
25 +//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
26 +We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
29 29  
30 30  == **Fancy Forum Answers** ==
31 31  
32 32  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:
33 33  
34 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
35 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
36 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
32 +* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
33 +* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
37 37  
38 38  == **Key takeaways** ==
39 39  
... ... @@ -41,11 +41,12 @@
41 41  
42 42  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
43 43  * If you have feedback or ideas for us, talk to the Platypus
44 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
41 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
45 45  * Clear your browser cache (Ctrl + Shift + Del)
46 46  * Check out the release notes [here]
47 47  * Start thinking about how the license tracker can aid your development
48 48  * Start thinking about major, minor, and patch
46 +* Upgrade to the latest build number
49 49  * Keep making great integrations
50 50  
51 51  Let's stay in touch and till next time!
... ... @@ -53,11 +53,6 @@
53 53  {{info}}
54 54  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
55 55  
56 -{{/info}}
57 -)))
58 -
59 -(((
60 -{{toc/}}
61 -)))
54 +~*~* Indicates a next-generation-architecture only feature.
55 +{{/info}})))((({{toc/}}))){{/container}}
62 62  {{/container}}
63 -{{/container}}