Skip to Content

Changes for page 193 - Fan Out

Last modified by Carlijn Kokkeler on 2024/04/18 13:18
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 82.1
edited by Erik Bakker
on 2023/02/14 14:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
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!** 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 a new event streaming graph and some updates to our platform in general.
6 6  
7 7  == **Start/Stop Flows** ~*~* ==
8 8  
... ... @@ -12,134 +12,46 @@
12 12  
13 13  [[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
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.
15 +After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
20 20  
21 -We offer alerting on five types.
17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
22 22  
23 -* Error message
24 -* Log message
25 -* Queue consumers
26 -* Messages in queue
27 -* Queue throughput
19 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
21 +== **Manage overview Event Streaming** ~*~* ==
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.
23 +To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
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.
36 -
37 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
38 -
39 -== **Debugger ** ~*~* ~* ==
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}}
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.
47 -
48 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
49 -
50 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
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.
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 73  == **Feedback items ** ==
74 74  
75 75  We have also solved other feedback items besides the flow designer's critical updates.
76 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.
31 +//__Topic configuration calculation__//
32 +With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
79 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.
34 +//__Make preparation step in deployment plan visible__//
35 +For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
82 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.
37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
85 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.
39 +//__3rd generation runtime debugger feedback__//
40 +We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
88 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.
42 +//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43 +As of now you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
91 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.
45 +//__User Management synchronization now happens in one step__//
46 +With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
94 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"]]
52 +* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53 +* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54 +* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
143 143  
144 144  == **Key takeaways** ==
145 145