Skip to Content

Changes for page 198 - Great Migration

Last modified by Carlijn Kokkeler on 2024/04/18 13:14
From version 44.1
edited by Erik Bakker
on 2022/11/08 10:05
Change comment: There is no comment for this version
To version 113.1
edited by Erik Bakker
on 2023/05/09 12:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +197 - Pay Attention
Content
... ... @@ -2,64 +2,55 @@
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 will release several impactful features and enablers to our community. Among others, the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients, enabling you to restore your flow to a previous version.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
6 6  
7 -== **Store - Next phase** ==
7 +== **Event streaming alerting** ==
8 8  
9 -This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible.
9 +With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
10 10  
11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
11 +The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
12 12  
13 -{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder, you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
13 +The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
14 14  
15 -== **New eMagiz Mendix Connector** ==
15 +[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
16 16  
17 -This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.
17 +The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
18 18  
19 -{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
19 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
20 20  
21 -== **Flow version restore** ~* ==
21 +The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
22 22  
23 -On top of that, we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way, you can quickly undo changes made that were incorrect.
23 +For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
25 +== **3rd generation improvements** ==
26 26  
27 -{{warning}}Note that the following restrictions apply when restoring to a previous version:
28 - * Changes made on definition and transformation level are **not** restored
29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
30 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
31 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
27 +//__Increased grace period for shutdown__//
28 +In this release, we have increased the grace period a container gets to shutdown before it is forcefully shutdown. This should reduce the chance of unwanted failover behavior to pop-up within your model.
32 32  
33 -== **Feedback items ** ==
30 +//__Update at once or not__//
31 +This release fixes 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.
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
33 +//__Improved user feedback while executing a deployment plan__//
34 +This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information of why this cannot be executed is shown to the user. This way they can take this information and act upon it instead of assuming everything went well.
36 36  
37 -//__Improved help texts Kafka component__//
38 -The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz.
36 +//__Improved auto-healing when running in a hybrid situation__//
37 +In situations where you run in a hybrid situation (i.e. partly next-gen and partly the current generation) we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next generation architecture.
39 39  
40 -//__Improved warning message when Message redelivery cannot be adequately executed__//
41 -We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning.
39 +== **Feedback items ** ==
42 42  
43 -//__See Flow Designer errors on the Create overview__//
44 -To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable.
41 +//__Make sure the message format can be viewed without "Start editing"__//
42 +With this release, we have ensured that when you navigate to Design -> System message you can see the message format (i.e. XML, JSON or EDI) without entering the "Start Editing" mode.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
44 +//__Various styling improvements in the flow testing functionality__//
45 +Various smaller styling improvements have been added to the flow testing functionality to improve the overall user experience. For a complete list and more details please check out the release notes.
47 47  
48 -{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
49 -
50 -== **Bug Fixes** ==
51 -
52 -//__Update Swagger File when changing the order of entities in gateway message__//
53 -In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this.
54 -
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  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:
58 58  
59 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
60 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
61 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
62 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
51 +* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
52 +* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
53 +* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
63 63  
64 64  == **Key takeaways** ==
65 65