Changes for page 210 - Deployment Delights

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-200 - Uncharted Territories
	1	+207 - Aligned State

Author

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

Content

...	...	@@ -2,60 +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 a lot of things that are unfortunately not quite ready to be released. As a result the output of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
	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		-== **Next generation improvements and bug fixes** ==
	7	+== **State Generation** ==
8	8
9		-//__Enhanced right-hand view within Deployment Plan context__//
10		-When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
	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 when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/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 timeout settings when deploying__//
15		-To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
	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		-{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	25	+Added support for `#JsonPath` usage in SpEL expressions.
18	18
19		-//__Detailed HTTP Statistics now show user info in specific additional cases__//
20		-To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
	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.
21	21
22		-{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	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.
23	23
24		-//__Improved loading speed of Manage Dashboard__//
25		-This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
	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.
26	26
27		-== **Store Improvements** ==
	36	+[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
28	28
29		-//__Importing in Design is improved__//
30		-We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
	38	+== **Feedback Items** ==
31	31
32		-== **Bug Fixes** ==
	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.
33	33
34		-//__Deprecated reminder pop-up removed__//
35		-We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
	43	+//__Save and cancel buttons__//
	44	+The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking.
36	36
37		-//__Improved selection area in Flow Designer__//
38		-When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
	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.
39	39
40		-//__Improved Kafka settings__//
41		-For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
	49	+
42	42
43		-{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
	51	+== **Bug Fixes** ==
44	44
	53	+
	54	+
45	45	== **Fancy Forum Answers** ==
46	46
47	47	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:
48	48
49		-* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
50		-* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||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"]]
51	51
	65	+
52	52	== **Key takeaways** ==
53	53
54		-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:
55	55
56	56	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57	57	* If you have feedback or ideas for us, talk to the Platypus
58		-* 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.
59	59	* Clear your browser cache (Ctrl + Shift + Del)
60	60	* Check out the release notes [here]
61	61	* Start thinking about how the license tracker can aid your development
...	...	@@ -68,6 +68,6 @@
68	68	{{info}}
69	69	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70
71		-~*~* Indicates a GEN3-only feature.
	85	+~*~* Indicates a next-generation-architecture only feature.
72	72	{{/info}})))((({{toc/}}))){{/container}}
73	73	{{/container}}