Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07

From version 81.1
edited by Erik Bakker
on 2023/02/13 14:00
Change comment: There is no comment for this version
To version 242.1
edited by Carlijn Kokkeler
on 2023/11/21 11:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,152 +2,76 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have the dynamic alerting and the debugger functionality.
5 +**Hi there, eMagiz developers!** We have done .....
6 6  
7 -== **Start/Stop Flows** ~*~* ==
7 +== **Next Generation Architecture Default** ==
8 +With this release, the next generation architecture will become the default. New models will use this generation as default.
8 8  
9 -{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
10 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
10 10  
11 -To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
12 +== **Cloud Template R11 - Single Lane** ==
13 +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
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
15 +== **Cloud Template R13 - Double Lane** ==
14 14  
15 -
16 -{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
17 -
18 -
19 - observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
20 20  
21 -We offer alerting on five types.
18 +== **Feedback Items** ==
22 22  
23 -* Error message
24 -* Log message
25 -* Queue consumers
26 -* Messages in queue
27 -* Queue throughput
20 +//__Unused properties overview__//
21 +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:
22 +* Not used by any runtime that is in the Create phase release.
23 +* Not required by a flow that is in the Create phase release.
24 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
26 +//__Send build requests asynchronously__//
27 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
30 30  
31 -These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
29 +//__Queue explorer milliseconds__//
30 +The queue browser now displays milliseconds in the timestamps.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
32 +//__Cancel and next buttons order__//
33 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
34 34  
35 -Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
35 +//__Unused images__//
36 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
36 36  
37 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
38 +//__Carwash logging__//
39 +A new logging feature enabling us to make better choices in encryption standards will be released.
38 38  
39 -== **Debugger ** ~*~* ~* ==
41 +//__Static alerts queue consumers__//
42 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
40 40  
41 -{{warning}}Note that this functionality only works when the following criteria are met.
42 -* Your JMS server is running on the 3rd generation runtime
43 -* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
44 -* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
44 +== **Bug Fixes** ==
45 45  
46 -As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
46 +//__Images rebuild__//
47 +We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
47 47  
48 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
49 +//__Flow Designer connection line__//
50 +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.
49 49  
50 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
52 +//__Portal for migrated models__//
53 +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.
51 51  
52 -Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
55 +//__Error channel inbounds__//
56 +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.
53 53  
54 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
55 -
56 -{{info}}Note the following limitations when working with the debugger.
57 - * Your entire model needs to be migrated to the 3rd generation runtime
58 - * Only **one** flow **per** runtime can be debugged **per** environment
59 - * There is only **one** overview in which **all** debugged messages are shown
60 - * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
61 - * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
62 - ** After five minutes the debug functionality will be shutdown automatically under water.
63 - ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
64 -
65 -== **Volume mapping - Network Share** ==
66 -
67 -This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
68 -
69 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
70 -
71 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
72 -
73 -== **Feedback items ** ==
74 -
75 -We have also solved other feedback items besides the flow designer's critical updates.
76 -
77 -//__Show status on machine level under Deploy Architecture__//
78 -With this release we are now able to show the status of the machine when opening the "Details" overview on machine level in Deploy -> Architecture.
79 -
80 -//__Improved validation feedback on non-supported WSS4J interceptor __//
81 -We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
82 -
83 -//__Improve help text in flow testing on Java classes__//
84 -We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
85 -
86 -//__Improved readibility of notification when trying to delete a runtime__//
87 -When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
88 -
89 -//__Improved sorting of missing properties overview__//
90 -We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
91 -
92 -//__Improved notification when error message cannot be found__//
93 -We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
94 -
95 -//__Additional lifecycle management overview__//
96 -We have added an additional lifecycle management overview to the portal in which users with enough permissions can get an overview of the lifecycle "state" of all customer models.
97 -
98 -//__Improved feedback when memory settings are negative__//
99 -We have added an additional check that validates whether memory settings on a specific container are of a negative value. In these cases you will be blocked from applying the changes to the environment as this won't lead to a working solution.
100 -
101 -//__Auto upgrade for a cloud template default to "ON"__//
102 -For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
103 -
104 -//__Removed an irrelevant refresh button on a flow designer component__//
105 -We have removed an irrelevant refresh button on the standard filter component.
106 -
107 -//__Notification list shows all notifications on default__//
108 -When navigating to the Notification overview in Manage under Alerting you will now see all notifications instead of a filtered list on a specific state.
109 -
110 -== **Bug fixes ** ==
111 -
112 -//__Keep selection when copying properties__//
113 -We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
114 -
115 -//__Check on security header improved for API Gateway__//
116 -We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
117 -
118 -//__Don't show systems with only "external" flows in Design__//
119 -We fixed a bug that caused systems to appear in Design in cases where there should be none.
120 -
121 -//__Fix styling of mendix login in some occurences__//
122 -When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
123 -
124 -//__Change timing of wake-up of cloud slots on Friday__//
125 -To prevent timing issues of waking up cloud slots on the Friday of our deployment we have changed the timing of when the cloud slots are woken up on Friday.
126 -
127 -//__Fixed a typo in the Topic statistics overview__//
128 -We fixed a typo in the topic statistics overview.
129 -
130 -//__Fixed a typo in the HTTP statistics overview__//
131 -We fixed a typo in the HTTP statistics overview.
132 -
133 -//__Activatation of release history when executing a deployment__//
134 -We ensured that the release history is activated when executing a deployment.
135 -
136 136  == **Fancy Forum Answers** ==
137 137  
138 138  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:
139 139  
140 -* [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
141 -* [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
142 -* [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||target="blank"]]
62 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
63 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
64 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
65 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
143 143  
67 +
144 144  == **Key takeaways** ==
145 145  
146 -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:
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:
147 147  
148 148  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
149 149  * If you have feedback or ideas for us, talk to the Platypus
150 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
74 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
151 151  * Clear your browser cache (Ctrl + Shift + Del)
152 152  * Check out the release notes [here]
153 153  * Start thinking about how the license tracker can aid your development
... ... @@ -160,6 +160,6 @@
160 160  {{info}}
161 161  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
162 162  
163 -~*~* Indicates a GEN3-only feature.
87 +~*~* Indicates a next-generation-architecture only feature.
164 164  {{/info}})))((({{toc/}}))){{/container}}
165 165  {{/container}}