Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+209 - Deployment Delights

Content

...	...	@@ -1,68 +1,59 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
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	+**Hi there, eMagiz developers!** We have...
6	6
7		-== **State Generation** ==
	8	+== **Alerts** ==
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	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
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).
	13	+//__Missing metrics alert__//
	14	+We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
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`.
	16	+== **Feedback Items** ==
24	24
25		-Added support for `#JsonPath` usage in SpEL expressions.
	18	+//__Container version overview__//
	19	+In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
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.
	21	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
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.
	23	+//__Unchanged containers__//
	24	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
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.
	26	+//__Rebuilding of images__//
	27	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
35	35
36		-[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
37	37
38		-== **Feedback Items** ==
	30	+== **Bug Fixes** ==
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.
	32	+//__Runtime metrics processing__//
	33	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
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.
	35	+//__Deployment plan__//
	36	+We solved a bug where a deployment step in the deployment plan could randomly get stuck.
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.
	38	+//__Store message merging__//
	39	+The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
48	48
49		-
	41	+//__View all store items__//
	42	+An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
50	50
51		-== **Bug Fixes** ==
	44	+//__Out of memory behavior__//
	45	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
52	52
	47	+//__Max fetch size__//
	48	+We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
	49	+
53	53
54		-
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"]]
	55	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
64	64
65		-
66	66	== **Key takeaways** ==
67	67
68	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:
...	...	@@ -83,5 +83,11 @@
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	85	~*~* Indicates a next-generation-architecture only feature.
86		-{{/info}})))((({{toc/}}))){{/container}}
	77	+{{/info}}
	78	+)))
	79	+
	80	+(((
	81	+{{toc/}}
	82	+)))
87	87	{{/container}}
	84	+{{/container}}