Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 197.1
edited by Carlijn Kokkeler
on 2023/10/23 16:07
Change comment: There is no comment for this version
To version 167.1
edited by Carlijn Kokkeler
on 2023/10/11 13:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +206 - Situational Deployment
Content
... ... @@ -2,114 +2,100 @@
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 few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6 6  
7 -== **State Generation** ==
7 +== **Deployment Plan** ==
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 +//__Improved deployment plan to make the process better and more predictable__//
10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
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).
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
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`.
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
24 24  
25 -Added support for `#JsonPath` usage in SpEL expressions.
18 +//__Properties tab__//
19 +We have removed the deprecated tab Properties in the Deploy phase.
26 26  
27 -//__New image version 2.0.0__//
28 -The above functionalities are features of the new image version 2.0.0. Important to note is that the library used for Code Mappings has been changed. Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0.
21 +//__Cleanup old images__//
22 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
29 29  
30 -//__Component pages__//
31 -Pages to add the new components have been created. Forms have been created nicely with proper help texts. The EHCache cache manager has been removed.
24 +//__Performance improvements for loading releases__//
25 +Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
32 32  
33 -== **Metrics Storage Duration** ==
34 -We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
27 +== **Store Improvements** ==
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
29 +//__Message definition elements order__//
30 +We fixed an issue that the order of message definition elements was changed after being imported.
37 37  
32 +//__Improting a store item with synchronous message definitions__//
33 +We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
34 +
35 +//__Importing store items containing static copies__//
36 +We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
37 +
38 38  == **Feedback Items** ==
39 39  
40 -//__Import from store__//
41 -The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
40 +//__Alerting manual pause__//
41 +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.
42 42  
43 -//__Save and cancel buttons placement__//
44 -The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
43 +//__Ordering of graphs in Manage__//
44 +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).
45 45  
46 -//__User session times__//
47 -The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
46 +//__UTC times in Grafana panels__//
47 +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.
48 48  
49 -//__Cancel and next buttons order//
50 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
49 +//__Update flow designer version__//
50 +The framework used in the flow designer has been updated to the latest version.
51 51  
52 -//__Data sink page__//
53 -The data sink page has been moved to the “Explore” tab.
52 +//__Carwash track TLS versions in logging__//
53 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
54 54  
55 -//__Unused images removal__//
56 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
55 +//__Moving channels in the flow designer__//
56 +Moving already attached channels in the flow designer has been made sligthly easier.
57 57  
58 -//__Flow Designer performance__//
59 -Performance improvements for the Flow Designer have been implemented.
58 +//__Topic sizes description change__//
59 +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.
60 60  
61 -//__Properties with special characters__//
62 -When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
61 +//__Password change notification__//
62 +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.
63 63  
64 -//__Hidden flow fragements__//
65 -When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
64 +//__Password comparison__//
65 +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.
66 66  
67 -//__Resources disappearances__//
68 -Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
67 +//__Inactive user alerting__//
68 +Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
69 69  
70 -//__Error channel for all inbounds__//
71 -If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
72 -We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
70 +//__Alphabetical sorting on user level in HTTP statistics__//
71 +Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
73 73  
74 -//__Highlighting resources__//
75 -The performance of highlighting resources of selected components is improved in Read only mode.
73 +//__SOAP Web services path__//
74 +Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
76 76  
77 77  == **Bug Fixes** ==
78 78  
79 -//__Topic and event-processor names__//
80 -The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
78 +//__Flow designer styling__//
79 +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.
81 81  
82 -//__System alignment__//
83 -The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
81 +//__Partial search for messages__//
82 +It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
84 84  
85 -//__Error checking__//
86 -Besides checking error header, the error trigger is now configured to check if an error message contains a term.
84 +//__Disk usage after cloud template update__//
85 +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.
87 87  
88 -//__Alerting__//
89 -For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
90 -For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
91 -The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
87 +//__Error handling migration__//
88 +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.
92 92  
93 -//__Unused containers__//
94 -Containers are set inactive when they are unused and removed in Design.
95 -
96 -//__Error popups when promoting a release version__//
97 -We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
98 -
99 -//__Memory leak__//
100 -A memory leak when using gen 3 metrics has been fixed.
101 -
90 +//__Importing Store content__//
91 +We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
92 +
102 102  == **Fancy Forum Answers** ==
103 103  
104 104  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:
105 105  
106 106  * [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
107 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
108 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
109 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
110 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
111 111  
112 -
113 113  == **Key takeaways** ==
114 114  
115 115  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: