Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 149.1
edited by Erik Bakker
on 2023/08/29 10:56
Change comment: There is no comment for this version
To version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +198 - Great Migration
Content
... ... @@ -2,39 +2,43 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
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.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
6 6  
7 -== **Feedback Items** ==
7 +== **3rd generation improvements and bug fixes** ==
8 8  
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.
9 +//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10 +Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
11 11  
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 connecting to a Kafka cluster but have become obsolete once you migrate.
12 +{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
14 14  
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}}
14 +//__Improved efficiency in deploying a release__//
15 +This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
16 16  
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 +//__Removed specific dependencies between Deploy Architecture and Releases__//
18 +In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
19 19  
20 -== **Bug Fixes** ==
20 +//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21 +This release fixes and 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.
21 21  
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).
23 +//__Improved migration behavior__//
24 +This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25 +A smoother migration of your JMS (and backup JMS) process.
26 +Shortening of names that otherwise would be too long, additional feedback given to the user.
27 +Feedback when the migration process is finished.
24 24  
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 +//__Additional checks when deploying__//
30 +This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
27 27  
28 28  == **Fancy Forum Answers** ==
29 29  
30 30  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:
31 31  
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"]]
36 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
34 34  
35 35  == **Key takeaways** ==
36 36  
37 -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:
41 +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:
38 38  
39 39  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
40 40  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -51,6 +51,6 @@
51 51  {{info}}
52 52  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53 53  
54 -~*~* Indicates a next-generation-architecture only feature.
58 +~*~* Indicates a GEN3-only feature.
55 55  {{/info}})))((({{toc/}}))){{/container}}
56 56  {{/container}}