Skip to Content

Changes for page 190 - Fast Forward

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

Summary

Details

Page properties
Content
... ... @@ -2,30 +2,30 @@
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!** 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 6  
7 7  == **Queue Browser** ~*~* ==
8 8  
9 9  {{warning}}Note that this functionality only works 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 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  
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 +To do so, we offer two options within this functionality. First, 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 the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
14 14  
15 15  [[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
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.
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 - ** 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.
20 + ** 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 - ** 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
22 + ** 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 - ** 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
24 + ** 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 - ** 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.
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 27  * Download
28 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
28 + ** 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  
... ... @@ -33,23 +33,23 @@
33 33  
34 34  == **Message Redelivery ** ~*~* ==
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}}
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 your environment.{{/warning}}
37 37  
38 38  [[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
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).
40 +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 under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
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.
42 +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.
43 43  
44 -On top of that we have added some additional functionality.
44 +On top of that, we have added some additional functionality.
45 45  
46 46  * Search option
47 47   ** Original queue name
48 48   ** Original message ID (which can be found as a header called jms_messageid in the error message view)
49 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.
50 + ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
51 51  * Download
52 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
52 + ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
53 53  
54 54  [[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
55 55  
... ... @@ -58,24 +58,24 @@
58 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.
59 59  
60 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.
61 +With this release, you can now 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.
62 62  
63 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.
64 +To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and 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.
65 65  
66 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.
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.
68 68  
69 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.
70 +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.
71 71  
72 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 73  
74 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.
75 +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.
76 76  
77 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"]]
78 +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"]]
79 79  
80 80  //__Performance improvement creating a release__//
81 81  With this release, we have improved the performance of creating a release.
... ... @@ -85,25 +85,25 @@
85 85  We have also solved other feedback items besides the flow designer's critical updates.
86 86  
87 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.
88 +We have made how we display sensitive information across the portal similar for various parts of the portal.
89 89  
90 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.
91 +We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
92 92  
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__//
96 +//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
97 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.
98 98  
99 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.
100 +We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
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.
103 +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.
106 +With this release, you can once again change property names upon importing a store item.
107 107  
108 108  == **Fancy Forum Answers** ==
109 109