Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+207 - Aligned State

Author

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

Content

...	...	@@ -2,125 +2,101 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
	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		-== **Queue Browser** ~*~* ==
	7	+== **State Generation** ==
8	8
9		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
	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	10
11		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
	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	12
13		-To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button.
	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`.
	24	+Added support for `#JsonPath` usage in SpEL expressions
14	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
16	16
17		-After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
	27	+== **Metrics Storage Duration** ==
	28	+
	29	+
	30	+
18	18
19		-* Delete the message from the queue (Explore option)
20		- ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21		-* Clear message from the wiretap queue (Wiretap option)
22		- ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23		-* Refresh messages list (both options)
24		- ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25		-* Save as test message
26		- ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27		-* Download
28		- ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
	32	+== **Feedback Items** ==
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	34	+//__Alerting manual pause__//
	35	+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.
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	37	+//__Ordering of graphs in Manage__//
	38	+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).
33	33
34		-== **Message Redelivery ** ~*~* ==
	40	+//__UTC times in Grafana panels__//
	41	+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.
35	35
36		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
	43	+//__Update flow designer version__//
	44	+The framework used in the flow designer has been updated, improving performance.
37	37
38		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
	46	+//__Carwash track TLS versions in logging__//
	47	+A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
39	39
40		-Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
	49	+//__Moving channels in the flow designer__//
	50	+Moving already attached channels in the flow designer has been made sligthly easier.
41	41
42		-Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
	52	+//__Topic sizes description change__//
	53	+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.
43	43
44		-On top of that we have added some additional functionality.
	55	+//__Password change notification__//
	56	+When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
45	45
46		-* Search option
47		- ** Original queue name
48		- ** Original message ID (which can be found as a header called jms_messageid in the error message view)
49		-* Save as test message
50		- ** By pressing this button you can save the message and use it in our flow testing functionality in Create.
51		-* Download
52		- ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
	58	+//__Password comparison__//
	59	+When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
53	53
54		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
	61	+//__Inactive user alerting__//
	62	+Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
55	55
56		-== **3rd generation runtime bolstering** ==
	64	+//__Alphabetical sorting on user level in HTTP statistics__//
	65	+Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
57	57
58		-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.
59	59
60		-//__Define memory settings for on-premise runtimes from Deploy Architecture__//
61		-With this release, you are now able to define the memory settings (and therefore the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes you need to create a new release and deploy it to actualize the changes on-premise.
	68	+== **Bug Fixes** ==
62	62
63		-//__Empty runtime feedback when deploying a release (or setting the release as active)__//
64		-To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in Deploy Architecture we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
	70	+//__Flow designer styling__//
	71	+The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
65	65
66		-//__Auto-fill namespaces for SOAP hosted webservices__//
67		-Based on your configuration in Design eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
	73	+//__Partial search for messages__//
	74	+It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
68	68
69		-//__Updated H2 database setting__//
70		-As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down.
	76	+//__Disk usage after cloud template update__//
	77	+In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
71	71
72		-{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
	79	+//__Error handling migration__//
	80	+If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
73	73
74		-//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
75		-As a replacement of the current HTTP settings context menu we have added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service) you now also can define whether the control bus needs to work for this runtime.
76		-
77		-//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
78		-With this release, we have added a context menu item that allows user to deploy the agent that is needed to run your 3rd generation architecture on-premise. For more information on how to install this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
79		-
80		-//__Performance improvement creating a release__//
81		-With this release, we have improved the performance of creating a release.
82		-
83		-== **Feedback items ** ==
84		-
85		-We have also solved other feedback items besides the flow designer's critical updates.
86		-
87		-//__Sensitive information stored in properties is masked __//
88		-We have made how we display sensitive information across the portal in the same manner for various parts of the portal.
89		-
90		-//__Importing "Private" store content to which you do not have access__//
91		-We have improved the user feedback a user will get when trying to import a "Private" store item that is not available to the user.
92		-
93		-
94		-== **Bug fixes ** ==
95		-
96		-//__Fix possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
97		-We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
98		-
99		-//__Synchronization of Event Streaming topic states__//
100		-We have fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
101		-
102		-//__Copy and paste default support objects__//
103		-With this release you can now copy and paste components without having to worry that additional support objects that already exist in your target flow are copied over and over into the same flow.
104		-
105		-//__Fix editability of properties when importing store items__//
106		-With this release you can once again change property names upon importing a store item.
107		-
108	108	== **Fancy Forum Answers** ==
109	109
110	110	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:
111	111
112		-* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
113		-* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
114		-* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
115		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
	86	+* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
	87	+* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
	88	+* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
	89	+* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
	90	+* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
116	116
	92	+
117	117	== **Key takeaways** ==
118	118
119		-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:
	95	+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:
120	120
121	121	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
122	122	* If you have feedback or ideas for us, talk to the Platypus
123		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	99	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
124	124	* Clear your browser cache (Ctrl + Shift + Del)
125	125	* Check out the release notes [here]
126	126	* Start thinking about how the license tracker can aid your development
...	...	@@ -133,6 +133,6 @@
133	133	{{info}}
134	134	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
135	135
136		-~*~* Indicates a GEN3-only feature.
	112	+~*~* Indicates a next-generation-architecture only feature.
137	137	{{/info}})))((({{toc/}}))){{/container}}
138	138	{{/container}}