Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-217 - Template Tango
	1	+210 - Deployment Delights

Content

...	...	@@ -3,51 +3,62 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In this release, new cloud templates for docker single and double lane are introduced. These templates enable the ability to clean H2 databases from the portal. Next to this, it is now possible to edit the trigger "More than 100 messages on queue over 10 minutes". Moroever, serveral copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version.
	6	+**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7	7
8		-== **Cloud Template R12 Docker - Single Lane** ==
9		-This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
	8	+== **Alerts** ==
10	10
11		-== **Cloud Template R14 Docker - Double Lane** ==
12		-This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
	10	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
13	13
	13	+//__Missing metrics alert__//
	14	+We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
	15	+
14	14	== **Feedback Items** ==
15		-//__Custom trigger__//
16		-The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
17	17
18		-[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
	18	+//__Improved release build process__//
	19	+When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
19	19
20		-//__Copy to clipboard buttons__//
21		-Copy to clipboard buttons have been added to various pages:
	21	+//__Container version overview__//
	22	+Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
22	22
23		- * Deploy agent pop-up
24		- * Create - Flow designer: Properties
25		- * Deploy - Property releases: Property details
	24	+[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
26	26
27		-[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
	26	+//_Improved deployment process_//
	27	+The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
28	28
29		-//__Reset H2 database__//
30		-For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following:
	29	+//__Rebuilding of images__//
	30	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
31	31
32		-* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
33		-* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
34		-* For on-premise runtimes, only a reset of the runtime is needed.
	32	+== **Bug Fixes** ==
35	35
36		-[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
	34	+//__Runtime metrics processing__//
	35	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
37	37
38		-== **Bug Fixes** ==
39		-//__Runtime overview improvements__//
40		-The runtime overview has been improved regarding checks on the runtime version.
	37	+//__Deployment plan__//
	38	+We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
41	41
	40	+//__View all store items__//
	41	+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.
	42	+
	43	+//__Out of memory behavior__//
	44	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
	45	+
	46	+//__Max fetch size__//
	47	+In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
	48	+
42	42	== **Fancy Forum Answers** ==
43	43
44	44	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:
45	45
46		-* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
47		-* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
	53	+* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
	54	+* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
	55	+* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
	56	+* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
	57	+* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
48	48
49		-== **Key Takeaways** ==
50	50
	60	+== **Key takeaways** ==
	61	+
51	51	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:
52	52
53	53	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -57,6 +57,7 @@
57	57	* Check out the release notes [here]
58	58	* Start thinking about how the license tracker can aid your development
59	59	* Start thinking about major, minor, and patch
	71	+* Upgrade to the latest build number
60	60	* Keep making great integrations
61	61
62	62	Let's stay in touch and till next time!
...	...	@@ -64,6 +64,7 @@
64	64	{{info}}
65	65	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66	66
	79	+~*~* Indicates a next-generation-architecture only feature.
67	67	{{/info}}
68	68	)))
69	69