Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 117.1
edited by Erik Bakker
on 2023/05/22 14:03
on 2023/05/22 14:03
Change comment:
There is no comment for this version
To version 150.1
edited by Erik Bakker
on 2023/08/29 10:57
on 2023/08/29 10:57
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 198-Great Migration1 +204 - Found It - Content
-
... ... @@ -2,50 +2,39 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In thelast few weeks, wehaveworkedhardonimprovingthe migrationtowardsour next-generationarchitecturewellas improvedthegeneralbehaviorwhenrunningonthenext-generationarchitecture.Furthermore, severalimprovementshavebeen made to ourown infrastructure toensurethat alldata flowingviathis infrastructurenowmoreand morecustomers aremigratingcanbe handled as goodifnotbetteras before.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. 6 6 7 -== ** 3rd generationimprovementsand bug fixes** ==7 +== **Feedback Items** == 8 8 9 -//__ "Stop" actionwhenrunninga hybridsituationis notcausing issues anymore__//10 - Before,it couldhappenwhenrunningadouble-lanesetupina hybridsituation(i.ekarafbasedruntimesontop of thenext-generationarchitecture)that thetopactiononsaid runtimewouldnot stoptheuntimebut"kill"it.Withthisreleasethat behavior ischanged.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 -{{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}} 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 -//__Removed certain dependencies between Deploy Architecture and Releases__// 15 -In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release. 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}} 16 16 17 -//__Improved validationerrors oninvalid configurationof HTTP outboundcomponents__//18 - This releasefixes andre-introducestheoptionto executeyouractionson theeMagiz perzoneorall atonce whenrunningina double-laneDocker setup.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. 19 19 20 -//__Improved migration behavior__// 21 -This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished. 20 +== **Bug Fixes** == 22 22 23 -//__ Improvedauto-healingwhenrunningina hybridsituation__//24 - Insituations whereyourunin a hybrid situation(i.e., partlynext-gen and partlythe currentgeneration),we haveimprovedtheauto-healingfunctionality incasean"outofmemory"appearsonaruntime runninginthecurrentgenerationbuton a next-generationarchitecture.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). 25 25 26 -//__ Improvedrollup and storageofetricswhenrunningyoursolutioninthenextgeneration archticture__//27 - Toimprovethestabilityofthe Managephaseand,inparticular,themetricswhenzoomingout ontheprovidedinformation,wehave made somestructural changesthat supportthis userfunctionalitybetter.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. 28 28 29 -{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}} 30 - 31 -== **Feedback items ** == 32 - 33 -//__Make sure the message format can be viewed without "Start editing"__// 34 -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. 35 - 36 -//__Various styling improvements in the flow testing functionality__// 37 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details. 38 - 39 39 == **Fancy Forum Answers** == 40 40 41 41 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: 42 42 43 -* [[ UpdateCore01withoutdowntime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]44 -* [[ "EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||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"]] 45 45 46 46 == **Key takeaways** == 47 47 48 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: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: 49 49 50 50 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 51 51 * If you have feedback or ideas for us, talk to the Platypus ... ... @@ -62,6 +62,6 @@ 62 62 {{info}} 63 63 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 64 64 65 -~*~* Indicates a GEN3-only feature.54 +~*~* Indicates a next-generation-architecture only feature. 66 66 {{/info}})))((({{toc/}}))){{/container}} 67 67 {{/container}}