Changes for page Container management

Summary

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

Details

Page properties

Content

...	...	@@ -1,13 +1,12 @@
1	1	{{container}}
2	2	{{container layoutStyle="columns"}}
3	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.
	4	+In a previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]], 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
9	9	== 1. Prerequisites ==
10		-- Intermediate knowledge of the eMagiz platform
	9	+* Intermediate knowledge of the eMagiz platform
11	11
12	12	== 2. Key concepts ==
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,10 +14,10 @@
14	14
15	15	**Some basic considerations:**
16	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
	16	+* In case a certain flow is made part of a release, but has not been assigned to any container than that release can not be activated or can not be set to active
18	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
	18	+* Exit gate flows are always put on the gateway container
	19	+* Event processors are always put on the streaming container
21	21
22	22	Please make sure that the maximum number of flows on any container is approx. 60 flows
23	23
...	...	@@ -46,7 +46,9 @@
46	46
47	47	If you are interested in this topic please read the help text eMagiz provides you in the container section in the Deploy phase and see the following link:
48	48
49		-
	48	+* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
	49	+** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
	50	+*** [[Creating a new Release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]]
50	50	* [[Container management (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22container+management%22||target="blank"]]
51	51	)))
52	52