Changes for page 198 - Great Migration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-191 - Fifty Fifty
	1	+197 - Pay Attention

Content

...	...	@@ -2,102 +2,69 @@
2	2	{{container layoutStyle="columns"}}(((
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.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
6	6
7		-== **Dynamic Alerts** ~*~* ==
	7	+== **Event streaming alerting** ==
8	8
9		-{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
	9	+With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
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 "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
	11	+The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
12	12
13		-We offer alerting on five types.
	13	+The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
14	14
15		-* Error message
16		-* Log message
17		-* Queue consumers
18		-* Messages in queue
19		-* Queue throughput
	15	+[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
20	20
21		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
	17	+The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
22	22
23		-These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
	19	+[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
24	24
25		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
	21	+The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
26	26
27		-Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
	23	+For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
28	28
29		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
	25	+== **3rd generation improvements** ==
30	30
31		-== **Debugger ** ~*~* ~* ==
	27	+//__Event Streaming statistics completion__//
	28	+In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
32	32
33		-{{warning}}Note that this functionality only works when the following criteria are met.
34		-* Your JMS server is running on the 3rd generation runtime
35		-* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
36		-* The beta image is activated
37		-* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
	30	+//__Deployments on next generation architecture__//
	31	+This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
38	38
39		-As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
	33	+//__Clean queues option__//
	34	+This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
40	40
41		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
42		-
43		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
44		-
45		-Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
46		-
47		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
48		-
49		-{{info}}Note the following limitations when working with the debugger.
50		- * Your entire model needs to be migrated to the 3rd generation runtime
51		- * Only **one** flow **per** runtime can be debugged **per** environment
52		- * There is only **one** overview in which **all** debugged messages are shown
53		- * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
54		- * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
55		- ** After five minutes the debug functionality will be shutdown automatically under water.
56		- ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
57		-
58		-== **Volume mapping - Network Share** ==
59		-
60		-This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
61		-
62		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
63		-
64		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
65		-
66	66	== **Feedback items ** ==
67	67
68		-We have also solved other feedback items besides the flow designer's critical updates.
	38	+//__On-premise containers are started upon slot wakeup__//
	39	+With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
69	69
70		-//__Improved validation feedback on non-supported WSS4J interceptor __//
71		-We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
	41	+//__Resource path is shown to the user__//
	42	+You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
72	72
73		-//__Improve help text in flow testing on Java classes__//
74		-We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
	44	+//__Flow designer improvements__//
	45	+With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
75	75
76		-//__Improved readibility of notification when trying to delete a runtime__//
77		-When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
	47	+//__Improved capabilities of a company contact__//
	48	+With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
78	78
79	79	== **Bug fixes ** ==
80	80
81		-//__Keep selection when copying properties__//
82		-We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
	52	+//__Optional API parameters are handled correctly__//
	53	+Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
83	83
84		-//__Check on security header improved for API Gateway__//
85		-We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
	55	+//__Without CDM rights nothing related to any data model can be edited anymore__//
	56	+With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
86	86
87		-//__Copy and paste default support objects__//
88		-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.
	58	+//__Improved sorting of Design and Deploy archticture__//
	59	+With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
89	89
90		-//__Fix editability of properties when importing store items__//
91		-With this release, you can once again change property names upon importing a store item.
92		-
93	93	== **Fancy Forum Answers** ==
94	94
95	95	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:
96	96
97		-* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
98		-* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
99		-* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
100		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
	65	+* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	66	+* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
	67	+* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
101	101
102	102	== **Key takeaways** ==
103	103