Container management

(((

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

6

Should you have any questions, please contact academy@emagiz.com.

7

8

== 1. Prerequisites ==

9

- Intermediate knowledge of the eMagiz platform

10

11

== 2. Key concepts ==

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

14

**Some basic considerations:**

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't be set to active

17

* Entry and Exit flow are always put on the system specific container

18

* Exit gate flows are always put on the gateway container

19

* Event processors are always put on the streaming container

20

21

Please make sure that the maximum number of flows on any container is approx. 60 flows

22

23

== 3. Container management ==

24

25

=== 3.1 Container assignments ===

26

27

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.

28

29

[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]

30

31

=== 3.2 Setting maximum number of flows per container ===

32

33

Bus owners 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 exceeds this limit.

34

35

[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]

36

37

== 4. Key takeaways ==

38

39

The key aspects are:

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

44

== 5. Suggested Additional Readings ==

45

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

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"]]

50

)))

51

52

((({{toc/}}))){{/container}}

53

author	version	line-number	content
		1	{{container}}
		2	{{container layoutStyle="columns"}}
		3	(((
		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
		6	Should you have any questions, please contact academy@emagiz.com.
		7
		8	== 1. Prerequisites ==
		9	- Intermediate knowledge of the eMagiz platform
		10
		11	== 2. Key concepts ==
		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
		14	Some basic considerations:
		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't be set to active
		17	* Entry and Exit flow are always put on the system specific container
		18	* Exit gate flows are always put on the gateway container
		19	* Event processors are always put on the streaming container
		20
		21	Please make sure that the maximum number of flows on any container is approx. 60 flows
		22
		23	== 3. Container management ==
		24
		25	=== 3.1 Container assignments ===
		26
		27	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.
		28
		29	[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]
		30
		31	=== 3.2 Setting maximum number of flows per container ===
		32
		33	Bus owners 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 exceeds this limit.
		34
		35	[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]
		36
		37	== 4. Key takeaways ==
		38
		39	The key aspects are:
		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
		44	== 5. Suggested Additional Readings ==
		45
		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
		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"]]
		50	)))
		51
		52	((({{toc/}}))){{/container}}
		53	{{/container}}

Wiki source code of Container management