Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 127.1
edited by Samet Kaya
on 2023/06/20 13:14
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 -200 - Uncharted Territories
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.SametKaya
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,61 +1,67 @@
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 a lot of things that are unfortunately not quite ready to be released. As a result the output of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Next generation improvements and bug fixes** ==
8 +== **TBD** ==
8 8  
9 -//__Enhanced right-hand view within Deployment Plan context__//
10 -When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
11 11  
12 -{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
13 13  
14 -//__Improved timeout settings when deploying__//
15 -To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
12 +== **Feedback Items** ==
16 16  
17 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
14 +//__Missing properties overview__//
15 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
18 18  
19 -//__Detailed HTTP Statistics now show user info in specific additional cases__//
20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
17 +ADD FIGURE
21 21  
22 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
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.
23 23  
24 -//__Improved loading speed of Manage Dashboard__//
25 -This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
26 26  
27 -== **Store Improvements** ==
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.
28 28  
29 -//__Importing in Design is improved__//
30 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
27 +//__Rebuilding of images__//
28 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
31 31  
32 32  == **Bug Fixes** ==
33 33  
34 -//__Deprecated reminder pop-up removed__//
35 -We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
32 +//__Runtime metrics processing__//
33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
36 36  
37 -//__Improved selection area in Flow Designer__//
38 -When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
35 +//__Deployment plan__//
36 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
39 39  
40 -//__Improved Kafka settings__//
41 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
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.
42 42  
43 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
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.
44 44  
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 +
45 45  == **Fancy Forum Answers** ==
46 46  
47 47  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:
48 48  
49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||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"]]
51 51  
57 +
52 52  == **Key takeaways** ==
53 53  
54 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
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:
55 55  
56 56  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57 57  * If you have feedback or ideas for us, talk to the Platypus
58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
59 59  * Clear your browser cache (Ctrl + Shift + Del)
60 60  * Check out the release notes [here]
61 61  * Start thinking about how the license tracker can aid your development
... ... @@ -68,6 +68,12 @@
68 68  {{info}}
69 69  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70 70  
71 -~*~* Indicates a GEN3-only feature.
72 -{{/info}})))((({{toc/}}))){{/container}}
77 +~*~* Indicates a next-generation-architecture only feature.
78 +{{/info}}
79 +)))
80 +
81 +(((
82 +{{toc/}}
83 +)))
73 73  {{/container}}
85 +{{/container}}