Skip to Content

Changes for page 204 - Found It

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +194 - Big Leap
Content
... ... @@ -2,117 +2,65 @@
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 have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
6 6  
7 -== **Queue Browser** ~*~* ==
7 +== **3rd generation improvements** ==
8 8  
9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
9 +//__Better feedback in error log when a corrupt stylesheet is encountered__//
10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
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.
12 +//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
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.
15 +//__Improved Manage Dashboard__//
16 +This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 +When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
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 +//__Improved process of deploy preparation__//
22 +With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
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.
24 +//__Improved migration of Streaming container__//
25 +When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
27 +//__Add History to Notifications in Manage__//
28 +To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
30 +//__Improved Manage phase for Event Streaming__//
31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
33 33  
34 -== **Message Redelivery ** ~*~* ==
33 +//__Improved help text for network volumes__//
34 +With this release we have improved the help text that explains network volumes and how to use them within our solution.
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}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
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).
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.
43 -
44 -On top of that we have added some additional functionality.
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.
53 -
54 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
55 -
56 -== **3rd generation runtime bolstering** ==
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.
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.
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.
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.
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 -We have also solved other feedback items besides the flow designer's critical updates.
40 +//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41 +With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
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.
43 +//__User Roles are sorted alphabetically__//
44 +All user roles under User Management are now also sorted alphabetically.
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.
46 +//__Name of keystore for user management now includes the environment__//
47 +To improve the naming of downloaded keystore that need to be distributed to external parties we have added the name of the environment to the filename. This way you can make a distinction between the various environments by looking at the filename.
92 92  
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.
51 +//__Consolidated upgrade process cloud template__//
52 +With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was actually happening in the cloud.
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.
54 +//__Ensure users can deploy release on environments they have edit rights on__//
55 +As of now users with only limited rights in Deploy, for example, only edit rights in Test can now activate and deploy releases that are ready for other environments but need to be deployed on the environment for which they have the rights to do so.
101 101  
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.
104 -
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.
107 -
108 108  == **Fancy Forum Answers** ==
109 109  
110 110  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:
111 111  
112 -* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
113 -* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
114 -* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
115 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
61 +* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62 +* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63 +* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
116 116  
117 117  == **Key takeaways** ==
118 118