Changes for page 210 - Deployment Delights
Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 244.1
edited by Carlijn Kokkeler
on 2023/11/21 11:31
on 2023/11/21 11:31
Change comment:
There is no comment for this version
To version 278.1
edited by Carlijn Kokkeler
on 2023/12/04 14:54
on 2023/12/04 14:54
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 -209 - Max Verstappen1 +209 - Deployment Delights - Content
-
... ... @@ -1,72 +1,57 @@ 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!** We have done.....6 +**Hi there, eMagiz developers!** We have... 6 6 7 - {{warning}}Pleasebeaware that for this release,because of the durationofthedeployment, weadvise you to check your TEST and ACCPcloud slots status, sinceyou might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead 5:00 AM UTC. {{/warning}}8 +== **Release Maintenance** == 8 8 9 -== **Next Generation Architecture Default** == 10 -With this release, the next generation architecture will become the default. New models will use this generation as default. 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 13 13 14 -== **Cloud Template R11 - Single Lane** == 15 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here 16 16 17 -== **Cloud Template R13 - Double Lane** == 18 18 19 - 20 20 == **Feedback Items** == 21 21 22 -//__Unused properties overview__// 23 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 24 -* Not used by any runtime that is in the Create phase release. 25 -* Not required by a flow that is in the Create phase release. 26 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 16 +//__Container version overview__// 17 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. 27 27 28 -//__Send build requests asynchronously__// 29 -The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 30 30 31 -//__ Queueexplorermilliseconds__//32 - Thequeuebrowser now displaysmilliseconds inthetimestamps.21 +//__Unchanged containers__// 22 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 33 33 34 -//__ Cancelandextbuttonsorder__//35 - The order of the cancel andnextbuttons whencreatinganew triggerhasbeen changedto increasealignmentacrossthe platform.Now, allcancel buttonsareplaced onthe rightof a'next' or 'save' button.24 +//__Rebuilding of images__// 25 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 36 36 37 -//__Unused images__// 38 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 39 39 40 -//__Carwash logging__// 41 -A new logging feature enabling us to make better choices in encryption standards will be released. 28 +== **Bug Fixes** == 42 42 43 -//__ Staticalertsqueue consumers__//44 - Alertingwillnowonlygeneratealertsfor queuesthatare created andmanagedbytheeMagizJMS server.30 +//__Runtime metrics processing__// 31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 45 45 46 -== **Bug Fixes** == 33 +//__Deployment plan__// 34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 47 47 48 -//__ Imagesrebuild__//49 - Wefixed an issue which causedtheeleasepreparationsteptotakelongertimethan necessaryandcausedthe machinedeploymentstepsto execute when theycouldbe skipped.36 +//__Store message merging__// 37 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages. 50 50 51 -//__ Flow Designerconnectionline__//52 - Inthe Flow Designer an issue has been fixed where theconnectionlinefordrawingchannelsdidworkwellwhenscrollingorzoomingin/out on thecanvas.39 +//__View all store items__// 40 +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. 53 53 54 -//__ Portalformigratedmodels__//55 -We fixeda rare case wherea runtimecouldnot start,orlogging,errors and metricscouldnotbeeenin the portalforamodel that hadjust migrated tothenext generation architecture.42 +//__Out of memory behavior__// 43 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 56 56 57 -//__Error channel inbounds__// 58 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 45 +//__Max fetch size__// 46 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects the behavior. 47 + 59 59 60 60 == **Fancy Forum Answers** == 61 61 62 62 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: 63 63 64 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 65 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 66 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 67 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 68 68 69 - 70 70 == **Key takeaways** == 71 71 72 72 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: ... ... @@ -87,5 +87,11 @@ 87 87 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 88 88 89 89 ~*~* Indicates a next-generation-architecture only feature. 90 -{{/info}})))((({{toc/}}))){{/container}} 75 +{{/info}} 76 +))) 77 + 78 +((( 79 +{{toc/}} 80 +))) 91 91 {{/container}} 82 +{{/container}}