Changes for page Container management
Last modified by Danniar Firdausy on 2024/09/18 13:01
From version 9.14
edited by Danniar Firdausy
on 2024/09/04 16:22
on 2024/09/04 16:22
Change comment:
There is no comment for this version
To version 9.12
edited by Danniar Firdausy
on 2024/09/04 16:18
on 2024/09/04 16:18
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,12 +1,12 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 -In aprevious[[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.4 +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 6 6 Should you have any questions, please contact academy@emagiz.com. 7 7 8 8 == 1. Prerequisites == 9 - *Intermediate knowledge of the eMagiz platform9 +- Intermediate knowledge of the eMagiz platform 10 10 11 11 == 2. Key concepts == 12 12 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 ... ... @@ -13,7 +13,7 @@ 13 13 14 14 **Some basic considerations:** 15 15 * 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 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 beactivated or can not beset to active16 +* 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 17 17 * Entry and Exit flow are always put on the system specific container 18 18 * Exit gate flows are always put on the gateway container 19 19 * Event processors are always put on the streaming container ... ... @@ -45,9 +45,7 @@ 45 45 46 46 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: 47 47 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"]] 48 + 51 51 * [[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"]] 52 52 ))) 53 53