Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 199.1
edited by Carlijn Kokkeler
on 2023/10/23 16:15
on 2023/10/23 16:15
Change comment:
There is no comment for this version
To version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
on 2022/12/06 15:57
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-Aligned State1 +189 - Private Eye - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -2,120 +2,81 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavedonemuchwork for stategeneration, so thatoucan derivemore informationfrom your data!Examplesare enrichment,aggregation,change detectionandduplicatedetection. Stategeneration functionalityis only accessiblefor modelswith an add-onstategenerationlicense.Nexttostate generation,severalimprovementsregardingthealignmentfcomponentshavebeen made.Moreover,performanceimprovementsand bugfixeshavebeenimplemented. Lastly,a changeinthemetrics storageurationhas beenperformed.5 +**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community. 6 6 7 -== **State Generation** == 7 +== **Private Store** == 8 +On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved). 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. 10 +{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/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). 12 +== **3rd generation runtime bolstering** == 22 22 23 - AddedsupportforSpELpropertyaccessors forXMLandJSON, meaning thatyou can readmessagepayloadsinSpEL expressionseasily.For example,toretrievethevalue for'id'inthefollowingJSON String: `{"id":"123"}`,thisSpELexpressionsuffices:`payload.id`.14 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 24 24 25 -Added support for `#JsonPath` usage in SpEL expressions. 16 +//__SOAP and REST web services migration, including splitting them__// 17 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal. 26 26 27 -//__ New imageversion2.0.0__//28 - Theabovefunctionalitiesarefeaturesofthe new image version2.0.0. Important to noteisthat thelibraryused for Code Mappingshasbeenchanged. Changedthelibrary used forCode Mappings.Any customerwith Gen3runtimes and code mappingsisrequiredto reset theirinfraflows priorto deployingon image2.0.0.19 +//__Changing SSL settings for 3rd generation runtime models works__// 20 +As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime. 29 29 30 -//__ Componentpages__//31 - Pagestoadd thenewcomponentshavebeen created.Forms havebeencreated nicelywith properhelptexts. TheEHCachecachemanagerhas been removed.22 +//__Improved migration for JMS flows__// 23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 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. 25 +{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}} 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]] 27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 28 +As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow. 37 37 38 -== **Feedback Items** == 30 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__// 31 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime. 39 39 40 -//__ Importfrom store__//41 - Thebutton'Importfrom Store'in Designwill directlyopenhestoresteadofshowinga pop askingwhetherthestoreshouldbe opened.33 +//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__// 34 +With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image. 42 42 43 -//__ Saveandcancelbuttons placement__//44 - Thesave andcancelbuttonshavebeenplacedslightlyfurtherapartfrom eachother to avoidmisclicking.36 +//__Added "Reset" functionality__// 37 +With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime. 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. 39 +== **Feedback items ** == 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. 41 +We have also solved other feedback items besides the flow designer's critical updates. 51 51 52 -//__ Datasinkpage__//53 - The datasinkpagehasbeen movedto the“Explore”tab.43 +//__Improved naming convention on Store related pages__// 44 +We have improved various display names using the merge functionality within our store offering. 54 54 55 -//__U nusedimages removal__//56 - Whenaeleaseisremoved,theelatedunusedimagesintheon-premisesmachineswillbemovedaswell.46 +//__Update security protocols for our internal architecture__// 47 +Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards. 57 57 58 -//__ FlowDesignerperformance__//59 - Performance improvementsfor theFlowDesigner havebeen implemented.49 +//__Improved read-only description for "if exists" constructions in Transformations__// 50 +To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does. 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. 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. 53 +== **Bug fixes ** == 66 66 67 -//__ Resourcesdisappearances__//68 - Resourceswould disappearintheflowdesignerwhenpressing Cancelonselectinganewresource. Withthis release,resources withoutanamewillnottriggererrormessageswhenusers selectcomponents.55 +//__Decent validation feedback when not filling in the property value__// 56 +We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality. 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. 58 +//__Incorrect resource locations__// 59 +We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime. 73 73 74 -//__ Highlightingresources__//75 - The performance ofhighlightingresourcesof selectedcomponentsis improvedinRead only mode.61 +//__Apply to environment in User Management performance improvement__// 62 +We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster. 76 76 77 -== **Bug Fixes** == 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. 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. 84 - 85 -//__Error checking__// 86 -Besides checking error header, the error trigger is now configured to check if an error message contains a term. 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. 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 - 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 -* [[ MessageRedeliveryblankerrormessage>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]107 -* [[ Timeouterrorkafkabatchcreation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]108 -* [[ SFTPConnectivity:Transferingawholefolderstructure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]109 -* [[ 3rdgenerationruntimewithdynamic filepickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]68 +* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]] 69 +* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]] 70 +* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]] 71 +* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]] 110 110 111 - 112 112 == **Key takeaways** == 113 113 114 -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:75 +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: 115 115 116 116 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 117 117 * If you have feedback or ideas for us, talk to the Platypus 118 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 79 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 119 119 * Clear your browser cache (Ctrl + Shift + Del) 120 120 * Check out the release notes [here] 121 121 * Start thinking about how the license tracker can aid your development ... ... @@ -128,6 +128,6 @@ 128 128 {{info}} 129 129 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 130 130 131 -~*~* Indicates a next-generation-architecture only feature.92 +~*~* Indicates a GEN3-only feature. 132 132 {{/info}})))((({{toc/}}))){{/container}} 133 133 {{/container}}