Changes for page 207 - Aligned State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 196.1
edited by Carlijn Kokkeler
on 2023/10/23 15:25
on 2023/10/23 15:25
Change comment:
There is no comment for this version
To version 157.1
edited by Carlijn Kokkeler
on 2023/10/10 14:06
on 2023/10/10 14:06
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -20 7-AlignedState1 +206 - Situational Deployment - Content
-
... ... @@ -2,74 +2,62 @@ 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 forstategeneration,so that you can derivemore informationfromyour data! Examples are enrichment,aggregation,changedetection and duplicateetection.Stategenerationfunctionalityis only accessiblefor models withan add-onstate generation license.Nextto stategeneration,severalimprovementsregardingthealignmentofcomponentshave been made. Moreover,performance improvementsand bug fixeshave been implemented.Lastly, a changeinthemetrics storageurationhas 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 -== ** StateGeneration** ==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. 20 + 21 +//__Cleanup old images__// 22 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 26 26 27 - //__Newimageversion2.0.0__//28 - Theabovefunctionalities 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.24 +== **Store Improvements** == 25 + 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. 27 +== **Feedback Items** == 32 32 33 - == **Metrics StorageDuration**==34 - Wewillchange theretentionofmonitoring data ofdifferentenvironments.Forminuteleveldata,itwill bekeptfor test,acceptanceandproductionenvironmentsfor 5, 7and30daysrespectively. Thentheminuteleveldatawillbe reducedtohourleveldata thenwill bestoredfortest, acceptanceandproductionfor3,6and12 monthsrespectively.29 +//__Alerting manual pause__// 30 +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. 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]] 32 +//__Ordering of graphs in Manage__// 33 +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). 37 37 38 -== **Feedback Items** == 35 +//__UTC times in Grafana panels__// 36 +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. 39 39 40 -//__ Import fromstore__//41 -The button 'ImportfromStore'in Design will directlyopen thestoreinsteadofshowing apop askingwhetherthestoreshouldbeopened.38 +//__Update flow designer version__// 39 +The framework used in the flow designer has been updated to the latest version. 42 42 43 -//__ Saveandcancelbuttonsplacement__//44 - Thesave andcancelbuttonshave beenplacedslightlyfurther apartfromeach othervoidmisclicking.41 +//__Carwash track TLS versions in logging__// 42 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 45 45 46 -//__ Usersession times__//47 - The user sessiontimes for3rdgeneration runtime dashboardshave beenextended,sothat the userisnotthrown out of themodelhenusingthe Managephaseforlongerthanan hour.44 +//__Moving channels in the flow designer__// 45 +Moving already attached channels in the flow designer has been made sligthly easier. 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. 51 - 47 +//__Topic sizes description change__// 48 +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. 52 52 50 + 51 + 53 53 == **Bug Fixes** == 54 -//__Topic and event-processor names__// 55 -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. 56 56 57 -//__System alignment__// 58 -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. 59 59 60 - 61 - 62 62 == **Fancy Forum Answers** == 63 63 64 64 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: 65 65 66 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 67 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 68 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 69 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 70 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 59 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 71 71 72 - 73 73 == **Key takeaways** == 74 74 75 75 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: