Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 151.1
edited by Erik Bakker
on 2023/09/13 07:02
Change comment: There is no comment for this version
To version 73.1
edited by Erik Bakker
on 2023/01/31 12:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +191 - Fifty Fifty
Content
... ... @@ -2,67 +2,131 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
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 -== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
7 +== **Dynamic Alerts** ~*~* ==
8 8  
9 -As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
9 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
10 10  
11 -== **Feedback Items** ==
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 -//__Improved Validation when migrating to the next-generation architecture__//
14 -To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
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.
15 15  
16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
15 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
17 17  
18 -//__Improved HTTP Statistics__//
19 -To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
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.
20 20  
21 -//__"Topic Full" alert restriction changed__//
22 -With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
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 inadvertently put many messages on a queue.
21 +* Clear message from the wiretap queue (Wiretap option)
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 +* Refresh messages list (both options)
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 +* 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 23  
24 -//__Improved performance Manage Dashboards__//
25 -We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
30 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
26 26  
27 -//__Show values on the runtime level in Deploy Architecture__//
28 -We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
32 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
29 29  
30 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31 -* JMS - The number of queues in the active release.
32 -* Messaging Container - The number of messaging integrations in the active release.
33 -* Messaging Connector - The number of messaging integrations related to this system in the active release.
34 -* API Gateway Container - The number of operations in the active release.
35 -* Event Streaming Container - The number of event processors in the active release.
34 +{{info}}The following restrictions apply to this functionality:
35 + * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
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 + ** 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}}
36 36  
37 -There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
40 +== **Debugger ** ~*~* ~* ==
38 38  
39 -== **Bug Fixes** ==
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}}
40 40  
41 -//__Improved information Queue Statistics__//
42 -Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
44 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
43 43  
44 -//__Gain the ability again to configure certificates in Deploy Architecture again__//
45 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
46 +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).
46 46  
47 -//__Ensure that differing container configurations deploy the correct configuration__//
48 -When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
48 +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.
49 49  
50 -//__Remove queurying options in Manage__//
51 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
50 +On top of that, we have added some additional functionality.
52 52  
52 +* Search option
53 + ** Original queue name
54 + ** Original message ID (which can be found as a header called jms_messageid in the error message view)
55 +* Save as test message
56 + ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
57 +* Download
58 + ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
59 +
60 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
61 +
62 +== **3rd generation runtime bolstering** ==
63 +
64 +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.
65 +
66 +//__Define memory settings for on-premise runtimes from Deploy Architecture__//
67 +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.
68 +
69 +//__Empty runtime feedback when deploying a release (or setting the release as active)__//
70 +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.
71 +
72 +//__Auto-fill namespaces for SOAP hosted webservices__//
73 +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.
74 +
75 +//__Updated H2 database setting__//
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 +
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}}
79 +
80 +//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
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 +
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"]]
85 +
86 +//__Performance improvement creating a release__//
87 +With this release, we have improved the performance of creating a release.
88 +
89 +== **Feedback items ** ==
90 +
91 +We have also solved other feedback items besides the flow designer's critical updates.
92 +
93 +//__Sensitive information stored in properties is masked __//
94 +We have made how we display sensitive information across the portal similar for various parts of the portal.
95 +
96 +//__Importing "Private" store content to which you do not have access__//
97 +We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
98 +
99 +
100 +== **Bug fixes ** ==
101 +
102 +//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
103 +We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
104 +
105 +//__Synchronization of Event Streaming topic states__//
106 +We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
107 +
108 +//__Copy and paste default support objects__//
109 +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.
110 +
111 +//__Fix editability of properties when importing store items__//
112 +With this release, you can once again change property names upon importing a store item.
113 +
53 53  == **Fancy Forum Answers** ==
54 54  
55 55  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:
56 56  
57 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
118 +* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
119 +* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
120 +* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
121 +* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
58 58  
59 59  == **Key takeaways** ==
60 60  
61 -Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
125 +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:
62 62  
63 63  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64 64  * If you have feedback or ideas for us, talk to the Platypus
65 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
129 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66 66  * Clear your browser cache (Ctrl + Shift + Del)
67 67  * Check out the release notes [here]
68 68  * Start thinking about how the license tracker can aid your development
... ... @@ -75,6 +75,6 @@
75 75  {{info}}
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
78 -~*~* Indicates a next-generation-architecture only feature.
142 +~*~* Indicates a GEN3-only feature.
79 79  {{/info}})))((({{toc/}}))){{/container}}
80 80  {{/container}}