Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-210 - Deployment Delights
	1	+206 - Situational Deployment

Content

...	...	@@ -1,62 +1,49 @@
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 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.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
7	7
8		-== **Alerts** ==
	7	+== **Deployment Plan** ==
9	9
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.
	9	+//__Improved deployment plan to make the process better and more predictable__//
	10	+The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
12	12
13		-//__Missing metrics alert__//
14		-We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
	12	+//__Editing release properties__//
	13	+With this release, it will be possible to change the description of a property by editing the property.
15	15
16		-== **Feedback Items** ==
17	17
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.
	16	+
	17	+
	18	+== **Store Improvements** ==
	19	+
20	20
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.
	21	+== **Feedback Items** ==
23	23
24		-[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
	23	+//__Alerting manual pause__//
	24	+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.
25	25
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.
	26	+//__Ordering of graphs in Manage__//
	27	+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).
28	28
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	32	== **Bug Fixes** ==
33	33
34		-//__Runtime metrics processing__//
35		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	32	+//__Gain the ability again to configure certificates in Deploy Architecture again__//
	33	+In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
36	36
37		-//__Deployment plan__//
38		-We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
	35	+//__Ensure that differing container configurations deploy the correct configuration__//
	36	+When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
39	39
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.
	38	+//__Remove queurying options in Manage__//
	39	+To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
42	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		-
49	49	== **Fancy Forum Answers** ==
50	50
51	51	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:
52	52
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"]]
	45	+* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
58	58
59		-
60	60	== **Key takeaways** ==
61	61
62	62	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:
...	...	@@ -77,11 +77,5 @@
77	77	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78	78
79	79	~*~* Indicates a next-generation-architecture only feature.
80		-{{/info}}
81		-)))
82		-
83		-(((
84		-{{toc/}}
85		-)))
	67	+{{/info}})))((({{toc/}}))){{/container}}
86	86	{{/container}}
87		-{{/container}}