Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 142.1
edited by Erik Bakker
on 2023/08/07 09:55
Change comment: There is no comment for this version
To version 202.1
edited by Carlijn Kokkeler
on 2023/10/24 11:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,73 +2,117 @@
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 few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
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.
6 6  
7 -== **Release Properties** ==
8 -As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
7 +== **State Generation'**'** ==
9 9  
10 -* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11 -* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
12 -* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
13 -* A, for most, new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
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.
14 14  
15 -{{info}}For more information, please check out the following microlearnings:
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).
16 16  
17 -* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19 -* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
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`.
20 20  
21 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 -{{/info}}
25 +Added support for `#JsonPath` usage in SpEL expressions.
23 23  
24 -== ** Manage - Graphs improvements ~*~* ** ==
25 -As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
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.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
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.
28 28  
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.
35 +
36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
37 +
29 29  == **Feedback Items** ==
30 30  
31 -//__Improved editability when testing in eMagiz without Edit rights in Create__//
32 -Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
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.
33 33  
34 -//__Improved auditability on Deploy Architecture__//
35 -To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
43 +//__Save and cancel buttons placement__//
44 +The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
36 36  
37 -//__Test your own exported store content__//
38 -We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
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.
39 39  
40 -{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
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.
41 41  
42 -//__Improved comparison of flows in the releases overview__//
43 -We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
52 +//__Data sink page__//
53 +The data sink page has been moved to the “Explore” tab.
44 44  
55 +//__Unused images removal__//
56 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
57 +
58 +//__Flow Designer performance__//
59 +Performance improvements for the Flow Designer have been implemented.
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.
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.
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.
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.
73 +
74 +//__Highlighting resources__//
75 +The performance of highlighting resources of selected components is improved in Read only mode.
76 +
45 45  == **Bug Fixes** ==
46 46  
47 -//__Improved validation on XPath header enricher__//
48 -To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
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.
49 49  
50 -//__Cancel behavior on flow testing property overview fixed__//
51 -We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
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.
52 52  
53 -//__Cancel behavior on flow fragment level when exporting store content__//
54 -We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
85 +//__Error checking__//
86 +Besides checking error header, the error trigger is now configured to check if an error message contains a term.
55 55  
56 -//__Adding numbers on containers in Deploy Architecture__//
57 -With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
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.
58 58  
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 +
59 59  == **Fancy Forum Answers** ==
60 60  
61 61  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:
62 62  
63 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
103 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
104 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
105 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
106 +* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
64 64  
108 +
65 65  == **Key takeaways** ==
66 66  
67 -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:
111 +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:
68 68  
69 69  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70 70  * If you have feedback or ideas for us, talk to the Platypus
71 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
115 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72 72  * Clear your browser cache (Ctrl + Shift + Del)
73 73  * Check out the release notes [here]
74 74  * Start thinking about how the license tracker can aid your development