Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
on 2023/05/22 15:07
Change comment:
There is no comment for this version
To version 574.4
edited by dfirdausy
on 2024/07/01 13:46
on 2024/07/01 13:46
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 198-Great Migration1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -1,53 +1,65 @@ 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 lastfewweeks, wehaveworkedhardonimprovingthemigrationtowardsournext-generationarchitecture and thegeneralbehaviorwhenrunning on the next-generationarchitecture.Furthermore, severalimprovementshavebeenmade toour infrastructureto ensurethatalldataflowingviathis infrastructurenowthatmore andmore customersaremigratingcanbehandledaswell,if notbetter,asbefore.6 +**Hi there, eMagiz developers!** In the past week, we focused our effort to improve the usability of our platform as well as addressing feedback we received from the community. More specifically, we improved user interface issues on several pages that are revolving around the description of help texts, external links in the help texts, the page layouts of help texts, pop-up pages, as well as <mention EPB-1332 here>. Next to that <mention improvements on debugging here, EZ-18118 and EZ-18285>. Finally, we also fixed an issue of incorrectly generated resource paths of Keystores and Trustores when creating an Event Processor for models that got migrated from the legacy runtime architecture to the current generation architecture. 6 6 7 -== **3rd generation improvements and bug fixes** == 8 +== **Feedback Items** == 9 +//__SwaggerUI default__// 10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. 8 8 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. 12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 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}} 14 +//__Used message types__// 15 +It is now possible to filter the message types in Capture on whether they are used. 13 13 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. 17 +[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]] 18 + 19 +//__Debugger duration__// 20 +Wiretaps and debugging sessions will now collect messages for ten minutes, this used to be five. Note that the JMS server needs to be updated in order to also store the messages for ten minutes instead of five. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 16 16 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. 22 +== **Bug Fixes** == 23 +//__SFTP sessions__// 24 +Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 19 19 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. 26 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]] 22 22 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. 28 28 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. 29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 31 31 31 +//__SMB outbound gateway__// 32 +The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 33 + 34 +//__TaskScheduler__// 35 +In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 36 + 37 +//__View XSLT__// 38 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 39 + 40 +//__Multipart/form-data HTTP request__// 41 +The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available. 42 + 32 32 == **Fancy Forum Answers** == 33 33 34 34 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: 35 35 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"]] 47 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 48 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 49 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 50 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 38 38 39 -== **Key takeaways** ==52 +== **Key Takeaways** == 40 40 41 -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:54 +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: 42 42 43 43 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 44 44 * If you have feedback or ideas for us, talk to the Platypus 45 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 58 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 46 46 * Clear your browser cache (Ctrl + Shift + Del) 47 -* Check out the release notes [here] 60 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]] 48 48 * Start thinking about how the license tracker can aid your development 49 49 * Start thinking about major, minor, and patch 50 -* Upgrade to the latest build number 51 51 * Keep making great integrations 52 52 53 53 Let's stay in touch and till next time! ... ... @@ -55,6 +55,11 @@ 55 55 {{info}} 56 56 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 58 -~*~* Indicates a GEN3-only feature. 59 -{{/info}})))((({{toc/}}))){{/container}} 70 +{{/info}} 71 +))) 72 + 73 +((( 74 +{{toc/}} 75 +))) 60 60 {{/container}} 77 +{{/container}}