Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 127.1
edited by Samet Kaya
on 2023/06/20 13:14
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 -200 - Uncharted Territories
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.SametKaya
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,66 +1,41 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
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 a lot of things that are unfortunately not quite ready to be released. As a result the output of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
6 +**Hi there, eMagiz developers!** This release...
6 6  
7 -== **Next generation improvements and bug fixes** ==
8 +== **Feedback Items** ==
8 8  
9 -//__Enhanced right-hand view within Deployment Plan context__//
10 -When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this 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"]].
11 11  
12 -{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
13 13  
14 -//__Improved timeout settings when deploying__//
15 -To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
16 -
17 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
18 -
19 -//__Detailed HTTP Statistics now show user info in specific additional cases__//
20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
21 -
22 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
23 -
24 -//__Improved loading speed of Manage Dashboard__//
25 -This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
26 -
27 -== **Store Improvements** ==
28 -
29 -//__Importing in Design is improved__//
30 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
31 -
32 32  == **Bug Fixes** ==
33 33  
34 -//__Deprecated reminder pop-up removed__//
35 -We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
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.
36 36  
37 -//__Improved selection area in Flow Designer__//
38 -When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
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.
39 39  
40 -//__Improved Kafka settings__//
41 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
42 -
43 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
44 -
45 45  == **Fancy Forum Answers** ==
46 46  
47 47  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:
48 48  
49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
26 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
51 51  
52 52  == **Key takeaways** ==
53 53  
54 -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:
30 +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:
55 55  
56 56  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57 57  * If you have feedback or ideas for us, talk to the Platypus
58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
34 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
59 59  * Clear your browser cache (Ctrl + Shift + Del)
60 60  * Check out the release notes [here]
61 61  * Start thinking about how the license tracker can aid your development
62 62  * Start thinking about major, minor, and patch
63 -* Upgrade to the latest build number
64 64  * Keep making great integrations
65 65  
66 66  Let's stay in touch and till next time!
... ... @@ -68,6 +68,11 @@
68 68  {{info}}
69 69  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70 70  
71 -~*~* Indicates a GEN3-only feature.
72 -{{/info}})))((({{toc/}}))){{/container}}
46 +{{/info}}
47 +)))
48 +
49 +(((
50 +{{toc/}}
51 +)))
73 73  {{/container}}
53 +{{/container}}