Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 58.1
edited by Erik Bakker
on 2023/01/18 08:57
Change comment: There is no comment for this version
To version 611.1
edited by Erik Bakker
on 2024/07/16 14:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +225 - Pop-up Party
Content
... ... @@ -1,107 +1,97 @@
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 -**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.
6 +**Hi there, eMagiz developers!** In this release, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
6 6  
7 -== **Queue Browser** ==
8 +== **Feedback Items** ==
9 +//__Alerting notification settings__//
8 8  
9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
11 +//__Process containers__//
12 +If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern.
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.
14 +//__Design settings__//
15 +When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
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 of your actual message that pass through the queue from the moment you pressed the Wiretap button.
17 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
19 +//__Untested images__//
20 + A warning will be shown when a release is activated on **Production** with a new runtime image version which has not been tested on acceptance before.
21 +
22 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.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.
24 +{{warning}}
25 +The following restrictions apply to this functionality:
26 +
27 +* When accepting the risk you accept the risk for the **whole** model.
28 +* If any release based on the same runtime image is already activated on Acceptance you will **not** be warned.{{/warning}}
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.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
31 +//__Infinispan Cache Manager__//
32 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
33 +
34 +//__Infinispan Cache Manager error message__//
35 +We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
31 31  
32 -== **3rd generation runtime bolstering** ==
37 +//__Flow bump__//
38 +When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
39 +
40 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
33 33  
34 -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.
42 +//__Unused support objects__//
43 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
35 35  
36 -//__SOAP and REST web services migration, including splitting them__//
37 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
45 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
46 +
47 +//__Deleting routes__//
48 +For clarity purposes, a confirmation pop-up will be shown when deleting routes.
38 38  
39 -//__Changing SSL settings for 3rd generation runtime models works__//
40 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
50 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
41 41  
42 -//__Improved migration for JMS flows__//
43 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
52 +//__Debug queue__//
53 +The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
54 +
55 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
56 +
57 +== **Bug Fixes** ==
58 +//__Internal server error__//
59 +The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
44 44  
45 -{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
61 +//__Namespace update__//
62 +Editing a namespace used in a message definition automatically updates the message definition & transformations.
46 46  
47 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
48 -As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
64 +//__Error pop-up__//
65 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
49 49  
50 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
51 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
67 +//__SMB inbound channel adapter__//
68 +The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
52 52  
53 -//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
54 -With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
70 +//__Heap memory__//
71 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
55 55  
56 -//__Added "Reset" functionality__//
57 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
73 +//__Classpath conflicts__//
74 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
58 58  
59 -== **Feedback items ** ==
60 -
61 -We have also solved other feedback items besides the flow designer's critical updates.
62 -
63 -//__Improved naming convention on Store related pages__//
64 -We have improved various display names using the merge functionality within our store offering.
65 -
66 -//__Update security protocols for our internal architecture__//
67 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
68 -
69 -//__Improved read-only description for "if exists" constructions in Transformations__//
70 -To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
71 -
72 -
73 -== **Bug fixes ** ==
74 -
75 -//__Decent validation feedback when not filling in the property value__//
76 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
77 -
78 -//__Incorrect resource locations__//
79 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
80 -
81 -//__Apply to environment in User Management performance improvement__//
82 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
83 -
84 84  == **Fancy Forum Answers** ==
85 85  
86 86  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:
87 87  
88 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
89 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
90 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
91 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
80 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
81 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
82 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
92 92  
93 -== **Key takeaways** ==
84 +== **Key Takeaways** ==
94 94  
95 -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:
86 +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:
96 96  
97 97  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
98 98  * If you have feedback or ideas for us, talk to the Platypus
99 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
90 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
100 100  * Clear your browser cache (Ctrl + Shift + Del)
101 -* Check out the release notes [here]
92 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
102 102  * Start thinking about how the license tracker can aid your development
103 103  * Start thinking about major, minor, and patch
104 -* Upgrade to the latest build number
105 105  * Keep making great integrations
106 106  
107 107  Let's stay in touch and till next time!
... ... @@ -109,6 +109,11 @@
109 109  {{info}}
110 110  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
111 111  
112 -~*~* Indicates a GEN3-only feature.
113 -{{/info}})))((({{toc/}}))){{/container}}
102 +{{/info}}
103 +)))
104 +
105 +(((
106 +{{toc/}}
107 +)))
114 114  {{/container}}
109 +{{/container}}