Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 88.1
edited by eMagiz
on 2023/02/28 13:18
Change comment: There is no comment for this version
To version 602.2
edited by CarlijnKokkeler
on 2024/07/16 14:33
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +225 - Pop-up Party
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,87 +1,93 @@
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!** In the last couple of weeks, we worked hard on API improvements and 3rd generation improvements for you all to see. Amongst the API improvements we now introduce the option to define REST/XML structures in your API gateway for your API callers to call. This brings more options to the user community in setting up the API Gateway structure in accordance with the needs and desires of the client. On top of that we have released several 3rd generation improvements. Amongst these we will add WS-Security functionality to the runtime and improvements on viewing release properties. Furthermore we have released new cloud templates to improve security in our current runtime and improve the auto-healing for 3rd generation runtime cloud slots. Last but not least we release the first adaptation of "State generation" that can be implemented with the help of us in your model. In the upcoming monts we will gather feedback from actual client cases and improve on this functionality.
6 +**Hi there, eMagiz developers!** In this release, a new runtime image (LINK) 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 -== **REST XML for API Gateway** ==
8 +== **Feedback Items** ==
9 +//__Alerting notification settings__//
10 +The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
8 8  
9 -{{warning}}Note that a decision needs to be made to select XML or JSON as default format for all your operations hosted in your API Gateway.{{/warning}}
12 +[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
10 10  
11 -To enhance your options when developing an API gateway that can be called by others we now introduce the option to select XML as the default message format on your API Gateway pattern. You can do this under Design -> Settings -> API Management. In here you can select and edit the settings.
14 +//__Process containers__//
15 +If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
17 +//__Design settings__//
18 +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.
14 14  
15 -Every operation made after this decision will default to XML (or JSON which is still the default). Should you want to support JSON on some operations and XML on others you can select a default and manually correct the mediaType for the requests and responses to which it matters.
20 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
22 +//__Untested images__//
23 + 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.
24 +
25 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
18 18  
19 -==**Cloud Template update** ==
27 +//__Infinispan Cache Manager__//
28 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
29 +
30 +//__Infinispan Cache Manager error message__//
31 +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 LINK is available.
20 20  
21 -We have released several new Cloud templates which will be installed via the auto-upgrade settings of your model (or manually in case not set).
33 +//__Flow bump__//
34 +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.
22 22  
23 -====Cloud Template R23 - Single Lane ====
36 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
24 24  
25 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 2nd generation runtime. This cloud template will update some specific security settings on these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
38 +//__Unused support objects__//
39 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
26 26  
27 -====Cloud Template R6 - Single Lane ====
41 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
42 +
43 +//__Deleting routes__//
44 +For clarity purposes, a confirmation pop-up will be shown when deleting routes.
28 28  
29 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
46 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
30 30  
31 -====Cloud Template R6 - Double Lane====
48 +//__Debug queue__//
49 +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.
50 +
51 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
52 +
53 +== **Bug Fixes** ==
54 +//__Internal server error__//
55 +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.
32 32  
33 -This release introduces a new cloud template for all our customers running in a double-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
57 +//__Namespace update__//
58 +Editing a namespace used in a message definition automatically updates the message definition & transformations.
34 34  
35 -== **WS-Security on the 3rd generation runtime** ~*~* ==
60 +//__Error pop-up__//
61 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
36 36  
37 -To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary.
63 +//__SMB inbound channel adapter__//
64 +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 LINK is available.
38 38  
39 -== **State Generation ~*~* ==
66 +//__Heap memory__//
67 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
40 40  
41 -With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
69 +//__Classpath conflicts__//
70 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
42 42  
43 -{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
44 -
45 -== **Feedback items ** ==
46 -
47 -//__Removed OData as option for an API Gateway operation__//
48 -With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
49 -
50 -//__Changes in API Gateway operation paths is automatically updated in Create__//
51 -When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
52 -
53 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
54 -
55 -== **Bug fixes ** ==
56 -
57 -//__Prevent endless loop in Deploy -> User Management__//
58 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
59 -
60 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
61 -
62 -//__Update error handling during migration to the 3rd generation runtime__//
63 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
64 -
65 65  == **Fancy Forum Answers** ==
66 66  
67 67  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:
68 68  
69 -* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
70 -* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
71 -* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
76 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
77 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
78 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
72 72  
73 -== **Key takeaways** ==
80 +== **Key Takeaways** ==
74 74  
75 -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:
82 +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:
76 76  
77 77  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  * If you have feedback or ideas for us, talk to the Platypus
79 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
86 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 80  * Clear your browser cache (Ctrl + Shift + Del)
81 -* Check out the release notes [here]
88 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
82 82  * Start thinking about how the license tracker can aid your development
83 83  * Start thinking about major, minor, and patch
84 -* Upgrade to the latest build number
85 85  * Keep making great integrations
86 86  
87 87  Let's stay in touch and till next time!
... ... @@ -89,6 +89,11 @@
89 89  {{info}}
90 90  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 91  
92 -~*~* Indicates a GEN3-only feature.
93 -{{/info}})))((({{toc/}}))){{/container}}
98 +{{/info}}
99 +)))
100 +
101 +(((
102 +{{toc/}}
103 +)))
94 94  {{/container}}
105 +{{/container}}