Skip to Content

Changes for page Container management

Last modified by Danniar Firdausy on 2024/09/18 13:01
From version 9.4
edited by Danniar Firdausy
on 2024/09/04 16:09
Change comment: There is no comment for this version
To version 9.12
edited by Danniar Firdausy
on 2024/09/04 16:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,6 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
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.
... ... @@ -16,8 +16,8 @@
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 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 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  
... ... @@ -38,17 +38,16 @@
38 38  == 4. Key takeaways ==
39 39  
40 40  The key aspects are:
41 - * Ensure to consider the container assigments when making releases
42 - * Considering setting the maximum number of flows on a process container to allow optimal performance of the container
40 +* Ensure to consider the container assigments when making releases
41 +* Considering setting the maximum number of flows on a process container to allow optimal performance of the container
42 +* Try to set the maximum of process flows to a low value to trigger the alert on the release level
43 43  
44 -
45 45  == 5. Suggested Additional Readings ==
46 46  
47 -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. Also read the following link:
48 -* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
49 -** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
50 -*** [[Setting up Exit gate (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-setting-up-exit-gate||target="blank"]]
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:
51 51  
48 +
49 +* [[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  
54 54  ((({{toc/}}))){{/container}}