Changes for page Flows Assignment

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Container management
	1	+intermediate-release-management-assigning-flows-2-containers

Author

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

Content

...	...	@@ -1,11 +1,17 @@
1	1	{{container}}
2	2	{{container layoutStyle="columns"}}
3	3	(((
	4	+
	5	+
	6	+= Managing releases - Best practice=
4	4
5	5	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.
6	6
7	7	Should you have any questions, please contact academy@emagiz.com.
8	8
	12	+- Last update: October 13th, 2021
	13	+- Required reading time: 5 minutes
	14	+
9	9	== 1. Prerequisites ==
10	10	- Intermediate knowledge of the eMagiz platform
11	11
...	...	@@ -13,11 +13,11 @@
13	13	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
14	14
15	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
	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
21	21
22	22	Please make sure that the maximum number of flows on any container is approx. 60 flows
23	23
...	...	@@ -25,7 +25,7 @@
25	25
26	26	=== 3.1 Container assignments ===
27	27
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.
	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.
29	29
30	30	[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]
31	31
...	...	@@ -42,8 +42,8 @@
42	42	== 5. Key takeaways ==
43	43
44	44	The key aspects are:
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
	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
47	47
48	48
49	49	== 6. Suggested Additional Readings ==