Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-185 - Get ready
	1	+200 - Uncharted Territories

Author

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

Content

...	...	@@ -2,46 +2,56 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
	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.
6	6
7		-==**Audit trail User Management**==
8		-Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
9		-
10		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
	7	+== **Next generation improvements and bug fixes** ==
11	11
12		-==**Next Generation Monitoring & Alerting engine**==
13		-In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
14		-
15		-* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
16		-* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
17		-* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
18		-* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
19		-* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
20		-
21		-
22		-=== **Improvements** ===
23		-
24		-* Performance Deployment plan
25		-When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
26		-
27		-* Flow Designer updates
28		-We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
29		-
30		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
31		-
32		-* Store
33		-We have fixed several smaller Store import issues to improve the user experience.
34		-
	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.
	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}}
	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.
	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}}
	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.
	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}}
	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.
	26	+
	27	+== **Store Improvements** ==
	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.
	31	+
	32	+== **Bug Fixes** ==
	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.
	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.
	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.
	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}}
	44	+
35	35	== **Fancy Forum Answers** ==
36	36
37		-As always, a gentle reminder to all 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:
	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:
38	38
39		-* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
40		-* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
	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"]]
41	41
42	42	== **Key takeaways** ==
43	43
44		-Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	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:
45	45
46	46	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
47	47	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -52,12 +52,11 @@
52	52	* Start thinking about major, minor, and patch
53	53	* Upgrade to the latest build number
54	54	* Keep making great integrations
55		-* Check out the new documentation portal.
56	56
57	57	Let's stay in touch and till next time!
58	58
59	59	{{info}}
60		-~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	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]]
61	61
62	62	~*~* Indicates a GEN3-only feature.
63	63	{{/info}})))((({{toc/}}))){{/container}}