Changes for page 202 - New Equilibrium

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-202 - New Equilibrium
	1	+190 - Fast Forward

Author

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

Content

...	...	@@ -1,74 +1,120 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
	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.
7	7
8		-== **Release Properties** ==
	7	+== **Queue Browser** ~*~* ==
9	9
10		-As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
	9	+{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
11	11
12		-* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
13		-* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
14		-* When adding or editing a property, you can **now** select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
15		-* A, for most, new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
	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.
16	16
17		-{{info}}
18		-For more information, please check out the following microlearnings:
	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.
19	19
20		-* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
21		-* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
22		-* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
	15	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
23	23
24		-Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
25		-{{/info}}
	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.
26	26
27		-== ** Manage - Graphs improvements ~*~* ** ==
	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.
28	28
29		-As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
	30	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
30	30
31		-[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
	32	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
32	32
33		-== **Feedback Items** ==
	34	+== **Message Redelivery ** ~*~* ==
34	34
35		-//__Improved editability when testing in eMagiz without Edit rights in Create__//
36		-Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
	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}}
37	37
38		-//__Improved auditability on Deploy Architecture__//
39		-To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
	38	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
40	40
41		-//__Test your own exported store content__//
42		-We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
	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).
43	43
44		-{{info}}
45		-In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]
46		-{{/info}}
	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.
47	47
48		-//__Improved comparison of flows in the releases overview__//
49		-We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
	44	+On top of that we have added some additional functionality.
50	50
51		-== **Bug Fixes** ==
	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.
52	52
53		-//__Improved validation on XPath header enricher__//
54		-To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
	54	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
55	55
56		-//__Cancel behavior on flow testing property overview fixed__//
57		-We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
	56	+== **3rd generation runtime bolstering** ==
58	58
59		-//__Cancel behavior on flow fragment level when exporting store content__//
60		-We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
	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.
61	61
62		-//__Adding numbers on containers in Deploy Architecture__//
63		-With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
	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.
64	64
	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.
	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.
	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.
	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}}
	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	+
65	65	== **Fancy Forum Answers** ==
66	66
67	67	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:
68	68
69		-* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
	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"]]
70	70
71		-== **Key Takeaways** ==
	117	+== **Key takeaways** ==
72	72
73	73	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:
74	74
...	...	@@ -76,7 +76,7 @@
76	76	* If you have feedback or ideas for us, talk to the Platypus
77	77	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78	78	* Clear your browser cache (Ctrl + Shift + Del)
79		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.202 - New Equilibrium.WebHome||target="blank"]]
	125	+* Check out the release notes [here]
80	80	* Start thinking about how the license tracker can aid your development
81	81	* Start thinking about major, minor, and patch
82	82	* Upgrade to the latest build number
...	...	@@ -87,12 +87,6 @@
87	87	{{info}}
88	88	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89	89
90		-~*~* Indicates a next-generation-architecture only feature.
91		-{{/info}}
92		-)))
93		-
94		-(((
95		-{{toc/}}
96		-)))
	136	+~*~* Indicates a GEN3-only feature.
	137	+{{/info}})))((({{toc/}}))){{/container}}
97	97	{{/container}}
98		-{{/container}}