Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 260.1
edited by Carlijn Kokkeler
on 2023/11/22 14:55
Change comment: There is no comment for this version
To version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +211 - Log Luminary
Content
... ... @@ -3,68 +3,58 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
6 +**Hi there, eMagiz developers!**
7 7  
8 -{{warning}}
9 -Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you 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 of 5:00 AM UTC.
10 -{{/warning}}
8 +== **TBD** ==
11 11  
12 -== **Quicker Deployment Plan Execution** ==
13 13  
14 -We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deployment plan will be finished much quicker now!
15 15  
16 -== **Next Generation Architecture Default** ==
17 -
18 -With this release, the next generation architecture will become the default. New models will use this generation as default.
19 -
20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
21 -
22 -== **Cloud Template R11 Docker - Single Lane** ==
23 -
24 -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>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
25 -
26 -== **Cloud Template R13 Docker - Double Lane** ==
27 -
28 -This release introduces a new cloud template for all our customers running in a double-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>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
29 -
30 30  == **Feedback Items** ==
31 31  
32 -//__Unused properties overview__//
33 -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:
14 +//__Missing properties overview__//
15 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
34 34  
35 -* Not used by any runtime that is in the Create phase release.
36 -* Not required by a flow that is in the Create phase release.
37 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
17 +ADD FIGURE
38 38  
39 -//__Queue explorer milliseconds__//
40 -The queue browser now displays milliseconds in the timestamps.
19 +//__Container version overview__//
20 +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.
41 41  
42 -//__Unused images__//
43 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
44 44  
45 -//__Carwash logging__//
46 -A new logging feature enabling us to make better choices in encryption standards will be released.
24 +//__Improved deployment process__//
25 +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.
47 47  
48 -//__Static alerts queue consumers__//
49 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
27 +//__Rebuilding of images__//
28 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
50 50  
51 51  == **Bug Fixes** ==
52 52  
53 -//__Flow Designer connection line__//
54 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
32 +//__Runtime metrics processing__//
33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
55 55  
56 -//__Portal for migrated models__//
57 -We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
35 +//__Deployment plan__//
36 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
58 58  
59 -//__Error channel inbounds__//
60 -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.
38 +//__View all store items__//
39 +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.
61 61  
41 +//__Out of memory behavior__//
42 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
43 +
44 +//__Max fetch size__//
45 +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.
46 +
62 62  == **Fancy Forum Answers** ==
63 63  
64 64  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:
65 65  
66 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
51 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
52 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
53 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
54 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
55 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
67 67  
57 +
68 68  == **Key takeaways** ==
69 69  
70 70  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: