Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 195.1
edited by Carlijn Kokkeler
on 2023/10/23 15:13
on 2023/10/23 15:13
Change comment:
There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
on 2022/11/21 12:31
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 207-AlignedState1 +188 - Close Encounters - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -2,74 +2,80 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavedone much work for stategeneration,sothat you can derive more informationfromyourdata! Examples are enrichment,aggregation,change detection and duplicatedetection.Stategenerationfunctionality is only accessible formodelswithan add-onstategenerationlicense. Nextto stategeneration,severalimprovements regarding thealignmentof componentshavebeenmade. Moreover,performanceimprovementsand bugfixeshavebeenimplemented. Lastly,a changeinthemetrics storageurationhas beenperformed.5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community. 6 6 7 -== ** StateGeneration** ==7 +== **3rd generation runtime bolstering** == 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 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it. 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 +//__Migration of JMS backup configuration improved__// 22 22 23 - Added support for SpEL property accessorsfor XML andJSON, meaningthat you canreadmessagepayloads in SpEL expressionseasily. For example,to retrieve the valuefor'id'in thefollowing JSON String: `{"id":"123"}`,this SpEL expressionsuffices: `payload.id`.13 +//__Prechecks on Upgrade option made available for 3rd generation runtime__// 24 24 25 -A dded supportfor `#JsonPath` usage inSpELexpressions.15 +//__Autogenerated exits can be deployed at once__// 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. 17 +//__Code mapping functionality available on 3rd generation runtime__// 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. 19 +//__Improved the performance of deploying or activating a release__// 32 32 33 -== **Metrics Storage Duration** == 34 -Manage - Monitoring: 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. 21 +//__Failing runtimes won't be restarted indefinetly anymore__// 35 35 36 - [[image:Main.Images.ReleaseBlog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]23 +== **Exportable Release Audit** ~* == 37 37 38 - ==**FeedbackItems**==25 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release. 39 39 40 -//__Import from store__// 41 -Design - Message Mapping: The button 'Import from Store' will directly open the store instead of showing a pop asking whether the store should be opened. 27 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 42 42 43 -//__Save and cancel buttons__// 44 -The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking. 29 +{{warning}}Note that the following restrictions apply when exporting an audit document: 30 + * Changes made on definition and transformation level are **not** restored 31 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022 32 + * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 33 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 45 45 46 -//__User session times__// 47 -Manage - Monitoring: 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. 35 +== **Feedback items ** == 48 48 49 - 37 +We have also solved other feedback items besides the flow designer's critical updates. 50 50 51 -== **Bug Fixes** == 39 +//__Data Sink Refactor__// 40 +We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately. 52 52 42 +//__Improved naming convention on Store related pages__// 43 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 53 53 45 +//__Press "Enter" to search on multiple pages__// 46 +In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows 54 54 48 +* Deploy → Deployment Plan 49 +* Deploy → Properties → History 50 +* Deploy → User Management → Roles 51 +* Manage → Error Messages → Error Messages 52 +* Manage → Error Messages → Flows with Error Messages 53 +* Manage → Error Messages → Exceptions of Error Messages 54 +* Manage → Log Entries 55 +* Manage → Alerts 56 +* Manage → Triggers 57 +* Manage → Tags – Cant find (only Gen2) 58 +* Manage → Notifications 59 +* Manage → Notification Settings 60 +* Manage → Data Usage → History 61 +* Manage → Code mappings → All tabs 62 + 55 55 == **Fancy Forum Answers** == 56 56 57 57 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: 58 58 59 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 60 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 61 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 62 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 63 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 67 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]] 68 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]] 69 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]] 70 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]] 64 64 65 - 66 66 == **Key takeaways** == 67 67 68 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:74 +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: 69 69 70 70 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 71 71 * If you have feedback or ideas for us, talk to the Platypus 72 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 78 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 73 73 * Clear your browser cache (Ctrl + Shift + Del) 74 74 * Check out the release notes [here] 75 75 * Start thinking about how the license tracker can aid your development ... ... @@ -82,6 +82,6 @@ 82 82 {{info}} 83 83 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 84 84 85 -~*~* Indicates a next-generation-architecture only feature.91 +~*~* Indicates a GEN3-only feature. 86 86 {{/info}})))((({{toc/}}))){{/container}} 87 87 {{/container}}