Changes for page Flows Assignment

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Flows Assignment
	1	+Container management

Author

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

Content

...	...	@@ -1,22 +1,60 @@
1		-{{container}}{{container layoutStyle="columns"}}(((
2		-This exercise will guide you in managing and assigning flows to containers.
3		-
4		-Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
	1	+{{container}}
	2	+{{container layoutStyle="columns"}}
	3	+(((
	4	+
	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.
5	5
	7	+Should you have any questions, please contact academy@emagiz.com.
	8	+
6	6	== 1. Prerequisites ==
	10	+- Intermediate knowledge of the eMagiz platform
7	7
8		-* Completed previous exercises and microlearnings
9		-* Access to an eMagiz model with Deploy rights
	12	+== 2. Key concepts ==
	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
10	10
11		-== 2. Exercise ==
	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
12	12
13		-Try to create a new flow that is not yet assigned to any containers in the Deploy phase. Then, navigate to Deploy->Containers, where you can change the advised number of flows that are deployed per container by clicking the "Change advised number of flows" button. Afterwards, you can try to create a new release. Here, normally, you can select the new flow to be included in the release via the visual interface in Deploy->Release. By doing this, eMagiz will automatically assign the flows to the corresponding containers.
	22	+Please make sure that the maximum number of flows on any container is approx. 60 flows
14	14
15		-However, to demonstrate what we have learned in this microlearning, try to assign the new flows manually via Deploy->Containers and then go to each containers to assign the corresponding flows (e.g., we assign onramp & offramps to the process containers, and entry & exit gate flows to the system containers). You can do this by clicking the "Add" button in each container and then select the flow you want to assign to this container. Lastly, you can proceed to activating this release.
	24	+== 3. Container management ==
16	16
17		-== 3. Solution ==
18		-In this short movie, you will find the workout of this exercise. Take a moment to review this one and compare it to your solution.
	26	+=== 3.1 Container assignments ===
19	19
20		-{{video attachment="intermediate-release-management-container-management.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
	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.
21	21
22		-)))((({{toc/}}))){{/container}}{{/container}}
	30	+[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]
	31	+
	32	+=== 3.2 Setting maxiumum number of flows per container ===
	33	+
	34	+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.
	35	+
	36	+[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]
	37	+
	38	+== 4. Assignment ==
	39	+
	40	+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.
	41	+
	42	+== 5. Key takeaways ==
	43	+
	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
	47	+
	48	+
	49	+== 6. Suggested Additional Readings ==
	50	+
	51	+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
	52	+
	53	+== 7. Silent demonstration video ==
	54	+
	55	+As this is a more theoretical microlearning we have no video for this.
	56	+
	57	+)))
	58	+
	59	+((({{toc/}}))){{/container}}
	60	+{{/container}}