Changes for page 213 - Joyful Journeys

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+207 - Aligned State

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -2,47 +2,74 @@
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 worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
	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		-== **3rd generation improvements and bug fixes** ==
	7	+== **State Generation** ==
8	8
9		-//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10		-Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
	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.
11	11
12		-{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
	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).
13	13
14		-//__Improved efficiency in deploying a release__//
15		-This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
	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`.
16	16
17		-//__Removed specific dependencies between Deploy Architecture and Releases__//
18		-In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
	25	+Added support for `#JsonPath` usage in SpEL expressions.
19	19
20		-//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21		-This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
	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.
22	22
23		-//__Improved migration behavior__//
24		-This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25		-A smoother migration of your JMS (and backup JMS) process.
26		-Shortening of names that otherwise would be too long, additional feedback given to the user.
27		-Feedback when the migration process is finished.
	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
29		-//__Additional checks when deploying__//
30		-This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
	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.
31	31
	36	+[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
	37	+
	38	+== **Feedback Items** ==
	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.
	42	+
	43	+//__Save and cancel buttons__//
	44	+The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking.
	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.
	48	+
	49	+
	50	+
	51	+== **Bug Fixes** ==
	52	+
	53	+
	54	+
32	32	== **Fancy Forum Answers** ==
33	33
34	34	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:
35	35
36		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	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"]]
38	38
	65	+
39	39	== **Key takeaways** ==
40	40
41		-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:
	68	+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:
42	42
43	43	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
44	44	* If you have feedback or ideas for us, talk to the Platypus
45		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	72	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
46	46	* Clear your browser cache (Ctrl + Shift + Del)
47	47	* Check out the release notes [here]
48	48	* Start thinking about how the license tracker can aid your development
...	...	@@ -55,6 +55,6 @@
55	55	{{info}}
56	56	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57	57
58		-~*~* Indicates a GEN3-only feature.
	85	+~*~* Indicates a next-generation-architecture only feature.
59	59	{{/info}})))((({{toc/}}))){{/container}}
60	60	{{/container}}