Wiki source code of 191 - Fifty Fifty

Last modified by Carlijn Kokkeler on 2024/04/18 13:19
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}(((
3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4
5 **Hi there, eMagiz developers!** In the last couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger functionality.
6
7 == **Dynamic Alerts** ~*~* ==
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
11 To enhance the 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.
12
13 We offer alerting on five types.
14
15 * Error message
16 * Log message
17 * Queue consumers
18 * Messages in queue
19 * Queue throughput
20
21 [[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
22
23 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.
24
25 [[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
26
27 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.
28
29 [[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
30
31 == **Debugger ** ~*~* ~* ==
32
33 {{warning}}Note that this functionality only works when the following criteria are met.
34 * Your JMS server is running on the 3rd generation runtime
35 * The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
36 * A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
37
38 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.
39
40 [[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
41
42 [[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
43
44 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.
45
46 [[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
47
48 {{info}}Note the following limitations when working with the debugger.
49 * Your entire model needs to be migrated to the 3rd generation runtime
50 * Only **one** flow **per** runtime can be debugged **per** environment
51 * There is only **one** overview in which **all** debugged messages are shown
52 * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
53 * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
54 ** After five minutes the debug functionality will be shutdown automatically under water.
55 ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
56
57 == **Volume mapping - Network Share** ==
58
59 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.
60
61 [[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
62
63 [[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
64
65 == **Feedback items ** ==
66
67 We have also solved other feedback items besides the flow designer's critical updates.
68
69 //__Show status on machine level under Deploy Architecture__//
70 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.
71
72 //__Improved validation feedback on non-supported WSS4J interceptor __//
73 We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
74
75 //__Improve help text in flow testing on Java classes__//
76 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.
77
78 //__Improved readibility of notification when trying to delete a runtime__//
79 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.
80
81 //__Improved sorting of missing properties overview__//
82 We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
83
84 //__Improved notification when error message cannot be found__//
85 We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
86
87 //__Additional lifecycle management overview__//
88 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.
89
90 //__Improved feedback when memory settings are negative__//
91 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.
92
93 //__Auto upgrade for a cloud template default to "ON"__//
94 For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
95
96 //__Removed an irrelevant refresh button on a flow designer component__//
97 We have removed an irrelevant refresh button on the standard filter component.
98
99 //__Notification list shows all notifications on default__//
100 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.
101
102 == **Bug fixes ** ==
103
104 //__Keep selection when copying properties__//
105 We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
106
107 //__Check on security header improved for API Gateway__//
108 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.
109
110 //__Don't show systems with only "external" flows in Design__//
111 We fixed a bug that caused systems to appear in Design in cases where there should be none.
112
113 //__Fix styling of mendix login in some occurences__//
114 When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
115
116 //__Change timing of wake-up of cloud slots on Friday__//
117 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.
118
119 //__Fixed a typo in the Topic statistics overview__//
120 We fixed a typo in the topic statistics overview.
121
122 //__Fixed a typo in the HTTP statistics overview__//
123 We fixed a typo in the HTTP statistics overview.
124
125 //__Activatation of release history when executing a deployment__//
126 We ensured that the release history is activated when executing a deployment.
127
128 == **Fancy Forum Answers** ==
129
130 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:
131
132 * [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
133 * [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
134 * [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||target="blank"]]
135
136 == **Key takeaways** ==
137
138 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:
139
140 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
141 * If you have feedback or ideas for us, talk to the Platypus
142 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
143 * Clear your browser cache (Ctrl + Shift + Del)
144 * Check out the release notes [[here>>doc:Main.Release Information.Portal.191 - Fifty Fifty.WebHome||target="blank"]]
145 * Start thinking about how the license tracker can aid your development
146 * Start thinking about major, minor, and patch
147 * Upgrade to the latest build number
148 * Keep making great integrations
149
150 Let's stay in touch and till next time!
151
152 {{info}}
153 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
154
155 ~*~* Indicates a GEN3-only feature.
156 {{/info}})))((({{toc/}}))){{/container}}
157 {{/container}}