Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 290.1
edited by Carlijn Kokkeler
on 2023/12/06 14:25
on 2023/12/06 14:25
Change comment:
There is no comment for this version
To version 435.1
edited by Carlijn Kokkeler
on 2024/04/08 11:19
on 2024/04/08 11:19
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 -21 0-DeploymentDelights1 +218 - Sprightly Spring - Content
-
... ... @@ -3,62 +3,68 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.6 +**Hi there, eMagiz developers!** 7 7 8 -== **Alerts** == 9 9 10 - //__Topicapproachingmaxsize alert__//11 - The alert‘topicapproaching maximum size’hasbeen temporarilydisableddueghnumberoffalsepositives.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. 12 12 13 -//__Missing metrics alert__// 14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 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 15 15 16 - ==**FeedbackItems**==23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change. 17 17 18 -//__Improved release build process__// 19 -When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed. 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 runtime>>doc:Main.Support.Migration Paths.migration-path-spring-6-migration||target="blank"]]. 20 20 21 -//__Container version overview__// 22 -Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release. 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. 23 23 24 -[[image:Main.Images.Release Blog.WebHome@release- blog-210-deployment-delights-container-overview.png]]31 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 25 25 26 -//_ Improved deployment process_//27 - The improved release buildprocess,as mentionedabove, brings another major improvement to the platform. Because container versions will not be updated regularly we canidentify during a deployment which containershouldgeta new container version. Only the onesthat should get a newversionwillbedeployed andrestarted, all other containers will not godown and keep running. Thisdecreasesthe deploymenttimeand improvestheperformance.33 +//__Copy to clipboard buttons__// 34 +Copy to clipboard buttons have been added to various pages: 28 28 29 -//__Rebuilding of images__// 30 -Changing the list of flows that should run on a container will now trigger the rebuilding of images. 36 + * Deploy agent pop-up 37 + * Create - Flow designer: Properties 38 + * Deploy - Property releases: Property details 31 31 32 - == **BugFixes**==40 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 33 33 34 -//__R untimemetricsprocessing__//35 - Thecollection andpublishing ofmetrics is nolonger synchronized acrosscontainers,whichimprovestheirprocessing.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 37 -//__Deployment plan__// 38 -We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. 45 +{{info}}Please note the following: 39 39 40 -//__View all store items__// 41 -An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 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. 42 42 43 -//__Out of memory behavior__// 44 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 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}} 45 45 46 -//__Max fetch size__// 47 -In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior. 53 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 48 48 55 +== **Bug Fixes** == 56 +//__Runtime overview improvements__// 57 +The runtime overview has been improved regarding checks on the runtime version. 58 + 49 49 == **Fancy Forum Answers** == 50 50 51 51 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: 52 52 53 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 54 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 55 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 56 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 57 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||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"]] 58 58 66 +== **Key Takeaways** == 59 59 60 -== **Key takeaways** == 61 - 62 62 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: 63 63 64 64 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -68,7 +68,6 @@ 68 68 * Check out the release notes [here] 69 69 * Start thinking about how the license tracker can aid your development 70 70 * Start thinking about major, minor, and patch 71 -* Upgrade to the latest build number 72 72 * Keep making great integrations 73 73 74 74 Let's stay in touch and till next time! ... ... @@ -76,7 +76,6 @@ 76 76 {{info}} 77 77 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 78 78 79 -~*~* Indicates a next-generation-architecture only feature. 80 80 {{/info}} 81 81 ))) 82 82