Changes for page 224 - Summer Sonata
Last modified by dfirdausy on 2024/07/04 10:01
From version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
on 2023/06/05 14:27
Change comment:
There is no comment for this version
To version 437.1
edited by CarlijnKokkeler
on 2024/04/08 11:20
on 2024/04/08 11:20
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 -1 99-HomeImprovements1 +218 - Sprightly Spring - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,58 +1,79 @@ 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 improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Next generation improvements and bug fixes** == 8 8 9 - //__Enhancedoverviewofthe HTTP Statistics__//10 -As o fnowallresourcesthat havebeen calledatleast oncesince deployingthemwillnow show up in theleft-bottom graph of theHTTP Statistics.This willmakeiteasiertoseewhethera particular operationwascalledwithinatimeframe. Ontop of thatitmakes comparingdata onvarious operations easier. In here you can also filteron one (by pressingthe+ icon) ormorebyclicking on thefilter icon.Incaseyouwanttosortthetable in adifferentmanneryoucanclick onthename ofthecolumnonwhichyouwanttosort.9 +== **Spring 6 Migration** == 10 +As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in our release that will be released on April 11th, 2024, which is this release. 11 11 12 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 12 +Configurations that contain any one of the listed components below are automatically migrated to Spring 6: 13 +* JDBC BoneCP data source 14 +* SSL web service message sender 15 +* Web service outbound gateway 16 +* SFTP session factory 17 +* HTTP components message sender 18 +* Job manager 19 +* Credentials 20 +* Simple job launcher 21 +* Default SFTP session factory 14 14 15 - {{info}}Notethatthisfixispart ofanew runtimeimagefor thenext-generationruntimes.Therelease notesofthiscanbe found [[here>>doc:Main.ReleaseInformation.RuntimeImages.WebHome||target="blank"]]{{/info}}23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change. 16 16 17 -//__Forced congestion control__// 18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 25 +In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration||target="blank"]]. 19 19 27 +== **Feedback Items** == 28 +//__Dynamic trigger__// 29 +The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger. 20 20 21 -//__Improved validation errors on the invalid configuration of HTTP outbound components__// 22 -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. 31 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 23 23 24 -//__Improved migration behavior__// 25 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are: 26 -A smoother migration of your JMS (and backup JMS) process. 27 -Shortening of names that otherwise would be too long, additional feedback given to the user. 28 -Feedback when the migration process is finished. 33 +//__Copy to clipboard buttons__// 34 +Copy to clipboard buttons have been added to various pages: 29 29 30 -//__Additional checks when deploying__// 31 -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. 36 + * Deploy agent pop-up 37 + * Create - Flow designer: Properties 38 + * Deploy - Property releases: Property details 32 32 33 - ==**StoreImprovements** ==40 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 34 34 35 -== **Event Streaming - Certificate Management** == 42 +//__Reset H2 database__// 43 +For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. 36 36 45 +{{info}}Please note the following: 46 + 47 +* Only H2 databases that are registered under the standard eMagiz data folder will be removed. 48 +* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. 49 +* For on-premise runtimes, only a reset of the runtime is needed. 50 + 51 +For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}} 52 + 53 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 54 + 55 +== **Bug Fixes** == 56 +//__Runtime overview improvements__// 57 +The runtime overview has been improved regarding checks on the runtime version. 58 + 37 37 == **Fancy Forum Answers** == 38 38 39 39 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: 40 40 41 -* [[ Howto determine thesystemdefinitionforthis samplemessageinJSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]42 -* [[ Instability in JMSconnection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]63 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 64 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]] 43 43 44 -== **Key takeaways** ==66 +== **Key Takeaways** == 45 45 46 -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:68 +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: 47 47 48 48 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 49 49 * If you have feedback or ideas for us, talk to the Platypus 50 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 72 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 51 51 * Clear your browser cache (Ctrl + Shift + Del) 52 52 * Check out the release notes [here] 53 53 * Start thinking about how the license tracker can aid your development 54 54 * Start thinking about major, minor, and patch 55 -* Upgrade to the latest build number 56 56 * Keep making great integrations 57 57 58 58 Let's stay in touch and till next time! ... ... @@ -60,6 +60,11 @@ 60 60 {{info}} 61 61 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 62 62 63 -~*~* Indicates a GEN3-only feature. 64 -{{/info}})))((({{toc/}}))){{/container}} 84 +{{/info}} 85 +))) 86 + 87 +((( 88 +{{toc/}} 89 +))) 65 65 {{/container}} 91 +{{/container}}