Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 315.1
edited by Carlijn Kokkeler
on 2023/12/21 14:40
Change comment: There is no comment for this version
To version 338.1
edited by Carlijn Kokkeler
on 2024/01/15 14:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +212 - Failover Fiesta
Content
... ... @@ -3,77 +3,28 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** This release...
7 7  
8 -== **TBD** ==
9 -
10 -
11 -
12 12  == **Feedback Items** ==
13 13  
14 -//__Runtime overview__//
15 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
10 +//__Failover setup__//
11 +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"]].
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
18 18  
19 -//__Missing properties overview__//
20 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
21 -
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
23 -
24 -//__Breaking changes pop-up__//
25 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
26 -
27 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
28 -
29 -//__External recipients emailaddress__//
30 -The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
31 -
32 -//__Broker queue metrics dashboards__//
33 -It is now possible to select the MQTT broker in the queue metrics dashboards.
34 -
35 -//__Runtime image version__//
36 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
37 -
38 -//__Runtime restart or redeploy overview__//
39 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
40 -
41 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
42 -
43 43  == **Bug Fixes** ==
44 44  
45 -//__Message throughput__//
46 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
16 +//__Message merging tool__//
17 +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.
47 47  
48 -//__Deployment execution error message__//
49 -In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
19 +//__Catalog topic definitions__//
20 +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.
50 50  
51 -//__Cloud template upgrade unjust rollback__//
52 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
53 -
54 -//__Missing log entries__//
55 -We improved crash handling so that log messages clearly show when and why a container failed to start.
56 -
57 -//__Runtime logging__//
58 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
59 -
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 -
63 -//__Feedback deployment plan__//
64 -
65 -
66 66  == **Fancy Forum Answers** ==
67 67  
68 68  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:
69 69  
70 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
71 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
72 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
73 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
74 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
26 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
75 75  
76 -
77 77  == **Key takeaways** ==
78 78  
79 79  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:
... ... @@ -85,7 +85,6 @@
85 85  * Check out the release notes [here]
86 86  * Start thinking about how the license tracker can aid your development
87 87  * Start thinking about major, minor, and patch
88 -* Upgrade to the latest build number
89 89  * Keep making great integrations
90 90  
91 91  Let's stay in touch and till next time!
... ... @@ -93,7 +93,6 @@
93 93  {{info}}
94 94  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
95 95  
96 -~*~* Indicates a next-generation-architecture only feature.
97 97  {{/info}}
98 98  )))
99 99