Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 430.1
edited by Carlijn Kokkeler
on 2024/03/25 16:45
on 2024/03/25 16:45
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 7-TemplateTango1 +210 - Deployment Delights - Content
-
... ... @@ -3,60 +3,62 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release, newcloudtemplatesfordockersingleanddockerdouble lane are introduced.These templatesenabletheability toclean H2 databasesfrom the portal. Next to this,it is nowpossibleto editthetrigger"More than100messagesonqueueover10 minutes".Moroever, serveralcopyto clipboardbuttons havebeen added. Lastly,theruntime overviewhasbeen improvedwithrespect to checksonthe runtimeversion.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. 7 7 8 - {{info}}Reminder!As announced in our previous [[release blog>>Main.Release Information.ReleaseBlogs.216 - Hack Heaven||target="blank"]], with the release of the 11th of April:8 +== **Alerts** == 9 9 10 - *TLSv1.0andTLSv1.1will bedeprecated.11 - *A major versionof our [[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]baseimageforll ourclientsrunning on the[[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]architecture will bereleased.10 +//__Topic approaching max size alert__// 11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives. 12 12 13 -For more information, please check out our [[release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]] from the previous release.{{/info}} 13 +//__Missing metrics alert__// 14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 14 14 15 -== **Cloud Template R12 Docker - Single Lane** == 16 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R12 Docker - Single Lane.WebHome||target="blank"]]. 16 +== **Feedback Items** == 17 17 18 - == **CloudTemplateR14Docker - Double Lane** ==19 - This release introducesa newnon-service affecting cloud templatefor allourcustomersrunning in a single-lanesetup. This cloud templateintroducesthe ability to cleanH2 databasesfrom theportal. Thecompletereleasenotes on thecloudtemplatecan befound[[here>>doc:Main.ReleaseInformation.CloudTemplates.R14Docker- DoubleLane.WebHome||target="blank"]].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. 20 20 21 -== **Feedback Items** == 22 -//__Dynamic trigger__// 23 -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. 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. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release-21 7-template-tango-custom-trigger.png]]24 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 26 26 27 -//_ _Copyoclipboard buttons__//28 - Copyto clipboardbuttons have beenaddedtovarious pages:26 +//_Improved deployment process_// 27 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance. 29 29 30 - * Deploy agent pop-up 31 - * Create - Flow designer: Properties 32 - * Deploy - Property releases: Property details 29 +//__Rebuilding of images__// 30 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 33 33 34 - [[image:Main.Images.ReleaseBlog.WebHome@release-217-template-tango-copy-to-clipboard.png]]32 +== **Bug Fixes** == 35 35 36 -//__Re setH2 database__//37 - Forour **[[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture,itnowpossibleto remove theeMagiz infraH2 database forconnector machines.34 +//__Runtime metrics processing__// 35 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 38 38 39 -{{info}}Please note the following: 37 +//__Deployment plan__// 38 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. 40 40 41 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed. 42 -* 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. 43 -* For on-premise runtimes, only a reset of the runtime is needed.{{/info}} 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. 44 44 45 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 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. 46 46 47 -== **Bug Fixes** == 48 -//__Runtime overview improvements__// 49 -The runtime overview has been improved regarding checks on the runtime version. 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. 50 50 51 51 == **Fancy Forum Answers** == 52 52 53 53 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: 54 54 55 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 56 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]] 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"]] 57 57 58 -== **Key Takeaways** == 59 59 60 +== **Key takeaways** == 61 + 60 60 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: 61 61 62 62 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -66,6 +66,7 @@ 66 66 * Check out the release notes [here] 67 67 * Start thinking about how the license tracker can aid your development 68 68 * Start thinking about major, minor, and patch 71 +* Upgrade to the latest build number 69 69 * Keep making great integrations 70 70 71 71 Let's stay in touch and till next time! ... ... @@ -73,6 +73,7 @@ 73 73 {{info}} 74 74 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 75 75 79 +~*~* Indicates a next-generation-architecture only feature. 76 76 {{/info}} 77 77 ))) 78 78