Changes for page Flows Assignment

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-intermediate-release-management-assigning-flows-2-containers
	1	+Managing releases - Best practice

Parent

...	...	@@ -1,1 +1,1 @@
1		-Main.WebHome
	1	+Main.eMagiz Academy.Microlearnings.Intermediate Level.Release Management.WebHome

Author

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

Content

...	...	@@ -1,65 +1,60 @@
1		-~{~{container}}
2		-~{~{container layoutStyle="columns"}}
3		-~(~(~(
4		-
5		-
6		-~= Managing releases - Best practice
	1	+{{container}}
	2	+{{container layoutStyle="columns"}}
	3	+(((
7	7
8	8	In previous microlearnings, we have already explained quite a lot about what releases are and how you should handle releases. In this microlearning, we will take a look at the management part of releases. This microlearning will focus on how to ensure flows are assigned to containers and why that is important.
9	9
10	10	Should you have any questions, please contact academy@emagiz.com.
11	11
12		-- Last update: October 13th, 2021
13		-- Required reading time: 5 minutes
14		-
15		-~== 1. Prerequisites ==
	9	+== 1. Prerequisites ==
16	16	- Intermediate knowledge of the eMagiz platform
17	17
18		-~== 2. Key concepts ==
	12	+== 2. Key concepts ==
19	19	This microlearning centers on containers. Containers in this context are the same as the runtimes of eMagiz that you will see in the runtime dashboard of eMagiz under Deploy - Runtime Dashboard. Each system in the model will create a runtime or container. You have to explain eMagiz what flows will run on what container. Notably important for the process container that holds the onramps and offramps - selection can be made how to spread these across one or more containers
20	20
21		-~*~*Some basic considerations:~*~*
22		-- Default behavior of new onramps and offramps is that these will be spread over all process containers. In some cases this desirable (2 containers - failover setup), but in some case one has to be specific and ensure the flows are put on the right process container
23		-- In case a certain flow is made part of a release, but has not been assigned to any container than that release can't be set to active
24		-- Entry and Exit flow are always put on the system specific container
25		-- Exit gate flows are always put on the Gateway Container
26		-- Event processors are always put on the Event Container
	15	+**Some basic considerations:**
	16	+* Default behavior of new onramps and offramps is that these will be spread over all process containers. In some cases this desirable (2 containers - failover setup), but in some case one has to be specific and ensure the flows are put on the right process container
	17	+* In case a certain flow is made part of a release, but has not been assigned to any container than that release can't be set to active
	18	+* Entry and Exit flow are always put on the system specific container
	19	+* Exit gate flows are always put on the Gateway Container
	20	+* Event processors are always put on the Event Container
27	27
28	28	Please make sure that the maximum number of flows on any container is approx. 60 flows
29	29
30		-~== 3. Container management ==
	24	+== 3. Container management ==
31	31
32		-~=== 3.1 Container assignments ===
	26	+=== 3.1 Container assignments ===
33	33
34		-Navigate to Deploy ~-~-> Containers. Select the runtime where the flow needs to be added and press Add. Select the flow and press Add once more in the pop-up.
	28	+Navigate to Deploy --> Containers. Select the runtime where the flow needs to be added and press Add. Select the flow and press Add once more in the pop-up.
35	35
36		-~[~[image~:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]
	30	+[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]
37	37
38		-~=== 3.2 Setting maxiumum number of flows per container ===
	32	+=== 3.2 Setting maxiumum number of flows per container ===
39	39
40	40	Busowners have the option to limit the number of flows on a process container. This option will impact the behavior of Release management where a release can't be promoted to a next environment or set as active in case the flows on the process containers exceeeds this limit.
41	41
42		-~[~[image~:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]
	36	+[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]
43	43
44		-~== 4. Assignment ==
	38	+== 4. Assignment ==
45	45
46	46	Check out if the best practices detailed above are applied within your (Academy) project. If not open up a discussion on why those choices are made to learn from that.
47	47
48		-~== 5. Key takeaways ==
	42	+== 5. Key takeaways ==
49	49
50	50	The key aspects are:
51		- - Ensure to consider the container assigments when making releases
52		- - Considering setting the maximum number of flows on a process container to allow optimal performance of the container
	45	+ * Ensure to consider the container assigments when making releases
	46	+ * Considering setting the maximum number of flows on a process container to allow optimal performance of the container
53	53
54	54
55		-~== 6. Suggested Additional Readings ==
	49	+== 6. Suggested Additional Readings ==
56	56
57	57	If you are interested in this topic please read the help text eMagiz provides you in the container section in the Deploy phase. Try to set the maximum of process flows to a low value to trigger the alert on the release level
58	58
59		-~== 7. Silent demonstration video ==
	53	+== 7. Silent demonstration video ==
60	60
61	61	As this is a more theoretical microlearning we have no video for this.
62	62
	57	+)))
63	63
64		-~(~(~(~{~{toc/}}~)~)~)~{~{/container}}~{~{/container}}
65		-
	59	+((({{toc/}}))){{/container}}
	60	+{{/container}}