Skip to Content

Changes for page 191 - Fifty Fifty

Last modified by Carlijn Kokkeler on 2024/04/18 13:19
From version 70.1
edited by Erik Bakker
on 2023/01/18 11:05
Change comment: There is no comment for this version
To version 74.1
edited by Erik Bakker
on 2023/01/31 12:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +191 - Fifty Fifty
Content
... ... @@ -2,108 +2,93 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
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 6  
7 -== **Queue Browser** ~*~* ==
7 +== **Dynamic Alerts** ~*~* ==
8 8  
9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
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 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 the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
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 12  
13 -To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button.
13 +We offer alerting on five types.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
15 +* Error message
16 +* Log message
17 +* Queue consumers
18 +* Messages in queue
19 +* Queue throughput
16 16  
17 -After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
21 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
18 18  
19 -* Delete the message from the queue (Explore option)
20 - ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21 -* Clear message from the wiretap queue (Wiretap option)
22 - ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23 -* Refresh messages list (both options)
24 - ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25 -* Save as test message
26 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27 -* Download
28 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
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.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
25 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
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.
33 33  
34 -== **Message Redelivery ** ~*~* ==
29 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
35 35  
36 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
31 +== **Debugger ** ~*~* ~* ==
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
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 +* The beta image is activated
37 +* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
39 39  
40 -Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
39 +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.
41 41  
42 -Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
41 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
43 43  
44 -On top of that we have added some additional functionality.
43 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
45 45  
46 -* Search option
47 - ** Original queue name
48 - ** Original message ID (which can be found as a header called jms_messageid in the error message view)
49 -* Save as test message
50 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create.
51 -* Download
52 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
45 +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 53  
54 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
47 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
55 55  
56 -== **3rd generation runtime bolstering** ==
49 +{{info}}Note the following limitations when working with the debugger.
50 + * Your entire model needs to be migrated to the 3rd generation runtime
51 + * Only **one** flow **per** runtime can be debugged **per** environment
52 + * There is only **one** overview in which **all** debugged messages are shown
53 + * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
54 + * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
55 + ** After five minutes the debug functionality will be shutdown automatically under water.
56 + ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
57 57  
58 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
58 +== **Volume mapping - Network Share** ==
59 59  
60 -//__Define memory settings for on-premise runtimes from Deploy Architecture__//
61 -With this release, you are now able to define the memory settings (and therefore the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes you need to create a new release and deploy it to actualize the changes on-premise.
60 +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.WebHome||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.
62 62  
63 -//__Empty runtime feedback when deploying a release (or setting the release as active)__//
64 -To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in Deploy Architecture we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
62 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
65 65  
66 -//__Auto-fill namespaces for SOAP hosted webservices__//
67 -Based on your configuration in Design eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
64 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
68 68  
69 -//__Updated H2 database setting__//
70 -As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down.
71 -
72 -{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
73 -
74 -//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
75 -As a replacement of the current HTTP settings context menu we have added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service) you now also can define whether the control bus needs to work for this runtime.
76 -
77 -//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
78 -With this release, we have added a context menu item that allows user to deploy the agent that is needed to run your 3rd generation architecture on-premise. For more information on how to install this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
79 -
80 -//__Performance improvement creating a release__//
81 -With this release, we have improved the performance of creating a release.
82 -
83 83  == **Feedback items ** ==
84 84  
85 85  We have also solved other feedback items besides the flow designer's critical updates.
86 86  
87 -//__Sensitive information stored in properties is masked __//
88 -We have made how we display sensitive information across the portal in the same manner for various parts of the portal.
70 +//__Improved validation feedback on non-supported WSS4J interceptor __//
71 +We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
89 89  
90 -//__Importing "Private" store content to which you do not have access__//
91 -We have improved the user feedback a user will get when trying to import a "Private" store item that is not available to the user.
73 +//__Improve help text in flow testing on Java classes__//
74 +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.
92 92  
76 +//__Improved readibility of notification when trying to delete a runtime__//
77 +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.
93 93  
94 94  == **Bug fixes ** ==
95 95  
96 -//__Fix possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
97 -We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
81 +//__Keep selection when copying properties__//
82 +We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
98 98  
99 -//__Synchronization of Event Streaming topic states__//
100 -We have fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
84 +//__Check on security header improved for API Gateway__//
85 +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.
101 101  
102 102  //__Copy and paste default support objects__//
103 -With this release you can now copy and paste components without having to worry that additional support objects that already exist in your target flow are copied over and over into the same flow.
88 +With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
104 104  
105 105  //__Fix editability of properties when importing store items__//
106 -With this release you can once again change property names upon importing a store item.
91 +With this release, you can once again change property names upon importing a store item.
107 107  
108 108  == **Fancy Forum Answers** ==
109 109