Changes for page 190 - Fast Forward
Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 72.1
edited by Erik Bakker
on 2023/01/19 09:02
on 2023/01/19 09:02
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.eMagiz - Content
-
... ... @@ -1,5 +1,6 @@ 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 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 and some minor enhancements. This release is characterized by the significant steps we took to release several major features on our 3rd generation runtime, including the queue browser and message redelivery functionality. ... ... @@ -6,7 +6,9 @@ 6 6 7 7 == **Queue Browser** ~*~* == 8 8 9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}} 10 +{{warning}} 11 +Note that this functionality only works when your JMS server is running on the 3rd generation runtime 12 +{{/warning}} 10 10 11 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 in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests. 12 12 ... ... @@ -17,29 +17,33 @@ 17 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. 18 18 19 19 * Delete the message from the queue (Explore option) 20 - 23 +** This means throwing away live data, which can be helpful in a test or acceptance environment where you inadvertently put many messages on a queue. 21 21 * Clear message from the wiretap queue (Wiretap option) 22 - 25 +** Once you are done with the analysis of a specific message in the wiretap functionality, you can clear it from the overview so it does not clutter the view anymore 23 23 * Refresh messages list (both options) 24 - 27 +** By pressing this button, you can refresh the list of messages displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first 25 25 * Save as test message 26 - 29 +** 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 27 * Download 28 - 31 +** By pressing this button, you can download the message and use it outside of the tooling should that be needed. 29 29 30 30 [[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]] 31 31 32 32 [[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]] 33 33 34 -{{info}}The following restrictions apply to this functionality: 37 +{{info}} 38 +The following restrictions apply to this functionality: 35 35 * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message" 36 36 * The wiretap functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in. 37 37 ** After five minutes the wiretap functionality will be shutdown automatically under water. 38 - ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}} 42 + ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch. 43 +{{/info}} 39 39 40 40 == **Message Redelivery ** ~*~* == 41 41 42 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment.{{/warning}} 47 +{{warning}} 48 +Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment. 49 +{{/warning}} 43 43 44 44 [[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]] 45 45 ... ... @@ -50,12 +50,12 @@ 50 50 On top of that, we have added some additional functionality. 51 51 52 52 * Search option 53 - 54 - 60 +** Original queue name 61 +** Original message ID (which can be found as a header called jms_messageid in the error message view) 55 55 * Save as test message 56 - 63 +** By pressing this button, you can save the message and use it in our flow testing functionality in Create. 57 57 * Download 58 - 65 +** By pressing this button, you can download the message and use it outside of the tooling should that be needed. 59 59 60 60 [[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]] 61 61 ... ... @@ -75,13 +75,15 @@ 75 75 //__Updated H2 database setting__// 76 76 As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down. 77 77 78 -{{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}} 85 +{{warning}} 86 +If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model 87 +{{/warning}} 79 79 80 80 //__Runtime settings option added to context menu on runtime level Deploy Architecture__// 81 81 As a replacement for the current HTTP settings context menu, we 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. 82 82 83 83 //__Deploy Agent option added to context menu on machine level Deploy Architecture__// 84 -With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]] 93 +With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide2.WebHome||target="blank"]] 85 85 86 86 //__Performance improvement creating a release__// 87 87 With this release, we have improved the performance of creating a release. ... ... @@ -140,5 +140,11 @@ 140 140 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 141 141 142 142 ~*~* Indicates a GEN3-only feature. 143 -{{/info}})))((({{toc/}}))){{/container}} 152 +{{/info}} 153 +))) 154 + 155 +((( 156 +{{toc/}} 157 +))) 144 144 {{/container}} 159 +{{/container}}