Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 188.1
edited by Carlijn Kokkeler
on 2023/10/23 14:45
Change comment: There is no comment for this version
To version 76.1
edited by Erik Bakker
on 2023/01/31 13:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +191 - Fifty Fifty
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,102 +2,110 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. State generation functionality is only accessible for models with an add-on state generation license. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
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 6  
7 -== **State Generation** ==
7 +== **Dynamic Alerts** ~*~* ==
8 8  
9 -//__New components__//
10 -The following components have been added:
11 -* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
12 -* Infinispan metadata outbound channel adapter: Used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
13 -* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
14 -* Duplicate detector: Support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
15 -* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
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}}
16 16  
17 -//__SpEL functions & JSON__//
18 -Added SpEL functions for:
19 -* Encoding & decoding Base64, Hex and hmac.
20 -* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
21 -* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
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.
22 22  
23 -Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
13 +We offer alerting on five types.
24 24  
25 -Added support for `#JsonPath` usage in SpEL expressions.
15 +* Error message
16 +* Log message
17 +* Queue consumers
18 +* Messages in queue
19 +* Queue throughput
26 26  
21 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
27 27  
28 -== **Metrics Storage Duration** ==
29 -
30 -
31 -
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.
32 32  
33 -== **Feedback Items** ==
25 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
34 34  
35 -//__Alerting manual pause__//
36 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
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.
37 37  
38 -//__Ordering of graphs in Manage__//
39 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
29 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
40 40  
41 -//__UTC times in Grafana panels__//
42 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
31 +== **Debugger ** ~*~* ~* ==
43 43  
44 -//__Update flow designer version__//
45 -The framework used in the flow designer has been updated, improving performance.
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}}
46 46  
47 -//__Carwash track TLS versions in logging__//
48 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
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.
49 49  
50 -//__Moving channels in the flow designer__//
51 -Moving already attached channels in the flow designer has been made sligthly easier.
41 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
52 52  
53 -//__Topic sizes description change__//
54 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
43 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
55 55  
56 -//__Password change notification__//
57 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
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.
58 58  
59 -//__Password comparison__//
60 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
47 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
61 61  
62 -//__Inactive user alerting__//
63 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
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}}
64 64  
65 -//__Alphabetical sorting on user level in HTTP statistics__//
66 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
58 +== **Volume mapping - Network Share** ==
67 67  
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.
68 68  
69 -== **Bug Fixes** ==
62 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
70 70  
71 -//__Flow designer styling__//
72 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
64 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
73 73  
74 -//__Partial search for messages__//
75 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
66 +== **Feedback items ** ==
76 76  
77 -//__Disk usage after cloud template update__//
78 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
68 +We have also solved other feedback items besides the flow designer's critical updates.
79 79  
80 -//__Error handling migration__//
81 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
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.
82 82  
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.
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.
78 +
79 +== **Bug fixes ** ==
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.
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.
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.
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 +
83 83  == **Fancy Forum Answers** ==
84 84  
85 85  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:
86 86  
87 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
88 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
89 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
90 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
91 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
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"]]
92 92  
93 -
94 94  == **Key takeaways** ==
95 95  
96 -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:
104 +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:
97 97  
98 98  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
99 99  * If you have feedback or ideas for us, talk to the Platypus
100 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
108 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
101 101  * Clear your browser cache (Ctrl + Shift + Del)
102 102  * Check out the release notes [here]
103 103  * Start thinking about how the license tracker can aid your development
... ... @@ -110,6 +110,6 @@
110 110  {{info}}
111 111  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
112 112  
113 -~*~* Indicates a next-generation-architecture only feature.
121 +~*~* Indicates a GEN3-only feature.
114 114  {{/info}})))((({{toc/}}))){{/container}}
115 115  {{/container}}