Changes for page 226 - Alerting Alchemy

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-191 - Fifty Fifty
	1	+225 - TBD

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,137 +1,94 @@
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 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	+**Hi there, eMagiz developers!**
6	6
7		-== **Dynamic Alerts** ~*~* ==
8	8
9		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
	9	+== **Feedback Items** ==
	10	+//__Alerting notification settings__//
	11	+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.
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 in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
	13	+[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
12	12
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	+//__Process containers__//
	16	+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.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	18	+//__Design settings__//
	19	+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.
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	+[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
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 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	+//__Untested images__//
	24	+ 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.
	25	+
	26	+[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	28	+//__Infinispan Cache Manager__//
	29	+We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
	30	+
	31	+//__Infinispan Cache Manager error message__//
	32	+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.
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	34	+//__Flow bump__//
	35	+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.
	36	+
	37	+[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
33	33
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}}
	39	+//__Unused support objects__//
	40	+Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
39	39
40		-== **Debugger ** ~*~* ~* ==
	42	+[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
	43	+
	44	+//__Deleting routes__//
	45	+For clarity purposes, a confirmation pop-up will be shown when deleting routes.
41	41
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}}
	47	+[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
43	43
44		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
	49	+//__Debug queue__//
	50	+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.
	51	+
	52	+[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
	53	+
	54	+== **Bug Fixes** ==
	55	+//__Internal server error__//
	56	+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.
45	45
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).
	58	+//__Namespace update__//
	59	+Editing a namespace used in a message definition automatically updates the message definition & transformations.
47	47
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.
	61	+//__Error pop-up__//
	62	+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		-On top of that, we have added some additional functionality.
	64	+//__SMB inbound channel adapter__//
	65	+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.
51	51
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.
	67	+//__Heap memory__//
	68	+The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
59	59
60		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
	70	+//__Classpath conflicts__//
	71	+We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
61	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		-
114	114	== **Fancy Forum Answers** ==
115	115
116	116	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:
117	117
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"]]
	77	+* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
	78	+* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
	79	+* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
122	122
123		-== **Key takeaways** ==
	81	+== **Key Takeaways** ==
124	124
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:
	83	+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:
126	126
127	127	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
128	128	* If you have feedback or ideas for us, talk to the Platypus
129		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	87	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
130	130	* Clear your browser cache (Ctrl + Shift + Del)
131		-* Check out the release notes [here]
	89	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
132	132	* Start thinking about how the license tracker can aid your development
133	133	* Start thinking about major, minor, and patch
134		-* Upgrade to the latest build number
135	135	* Keep making great integrations
136	136
137	137	Let's stay in touch and till next time!
...	...	@@ -139,6 +139,11 @@
139	139	{{info}}
140	140	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
141	141
142		-~*~* Indicates a GEN3-only feature.
143		-{{/info}})))((({{toc/}}))){{/container}}
	99	+{{/info}}
	100	+)))
	101	+
	102	+(((
	103	+{{toc/}}
	104	+)))
144	144	{{/container}}
	106	+{{/container}}