Skip to Content
Last modified by dfirdausy on 2024/09/27 09:18
From version 47.2
edited by dfirdausy
on 2024/09/27 09:16
Change comment: There is no comment for this version
To version 5.1
edited by Erik Bakker
on 2023/02/07 13:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Grouping - Deploy Possibilities
1 +eMagiz Deploy agent
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome
1 +Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,14 +1,9 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
4 -eMagiz flows, or more specifically, the flow's inbound component(s), can be grouped. Configuring this is explained [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]]. This functionality is mainly beneficial when faced with substantial maintenance or outage of systems connected to your eMagiz model.
1 +{{container}}{{container layoutStyle="columns"}}(((
5 5  
6 -Building on this functionality, you can even configure the group to run in an active/passive failover mode when you activate the multiple runtimes option on your runtime, and each separate runtime is deployed on another machine. The failover functionality is relevant not only in cases of server maintenance but also in that it can assist you when you want to exchange data with a system that allows only one active connection. Should this connection be business-critical, you can use this failover functionality to create a passive failover situation that will take over when the active connection breaks down (regardless of the reason).
3 +eMagiz runtimes can run on local, on-premises servers. Main reason is that some systems are only accessible from within the client's infrastructure. In such scenario's that on-premises server needs to be equipped with a linux based Docker installation.
7 7  
8 -This microlearning will focus on configuring the deployment plan to control various inbound components in a typical group and failover configuration.
5 +Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
9 9  
10 -If you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
11 -
12 12  == 1. Prerequisites ==
13 13  
14 14  * Intermediate knowledge of the eMagiz platform
... ... @@ -15,44 +15,24 @@
15 15  
16 16  == 2. Key concepts ==
17 17  
18 -This microlearning describes how to configure (parts of) your deployment plan to set up the grouping and, if needed, the failover functionality. The grouping functionality is relevant when faced with maintenance and outages of systems connected to your model. The failover functionality assists and allows you to have a fallback option on an active connection.
13 +This microlearning describes how the eMagiz Deploy agent is installed on the on-premises server where a eMagiz runtime should run on. Please note that the eMagiz Deploy agent requires a valid Docker installation on the on-premises server. The detailed install guide can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-installguide.WebHome||target="blank"]].
19 19  
20 -== 3. Deploy Possibilities ==
21 -=== 3.1. Group Deployment Step ===
22 22  
23 -To configure a Group deployment step, add a new one and choose Step type "Group". More information is required to configure the step. A container should be selected for which the inbounds will be stopped. The second requirement is the **exact** name of the group that should be affected by the deployment step. An action should be picked for the selected group. The options for a "Group" deployment step are to start or stop the inbound components within the group. Optionally, a description can be added.
16 +== 3. eMagiz Docker agent installation ==
24 24  
25 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-group-deployment-step.png]]
18 +eMagiz needs to install a specific agent in the Docker instance that allows to download runtime images that needs to be installed on the Docker instance. The specific command to run inside the Docker instance is specific for the machine that is configured inside eMagiz Design & Deploy Architectures. It can be found inside the eMagiz iPaaS portal under Deploy Architecture. At the runtime connector, there is a right click option called Deploy Agent. That presents either the command or the location where that agent is installed.
26 26  
27 -{{info}}Note that when you activate the stop action in a failover setup (on the leader container), it will trigger the failover behavior on the follower container{{/info}}
20 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]]
28 28  
22 +After installing the agent, you can use the Docker cheat sheet below to see if the docker containers are running and/or images are available.
23 +
29 29  == 4. Key takeaways ==
30 30  
31 -* Grouping is beneficial when external systems go through maintenance or downtime.
32 -* Failover can have the additional benefit of having a fallback scenario while still adhering to the requirement that there can only be one active connection at a time.
33 -* The role naming in both grouping and failover is crucial. The group name needs to match **exactly** to make it work.
34 -* You can control group and failover steps from the deployment plan.
35 -* Container inbounds can have a different failover status.
26 +* The eMagiz Docker agent needs to be installed to allow runtime to be installed on the on-premises server
36 36  
37 -== 5. Suggested Additional Readings ==
28 +== 6. Suggested Additional Readings ==
38 38  
39 -If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links:
30 +No suggested additional readings for this microlearning.
40 40  
41 -* [[eMagiz Store (Menu)>>doc:Main.eMagiz Store.WebHome||target="blank"]]
42 -** [[Accelerators (Navigation)>>doc:Main.eMagiz Store.Accelerators.WebHome||target="blank"]]
43 -*** [[Active/Passive Failover (Explanation)>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.WebHome||target="blank"]]
44 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
45 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
46 -*** [[Deploy a release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]
47 -*** [[Setting up a deployment plan (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-setup-deployment-plan-gen3||target="blank"]]
48 -* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
49 -** [[Grouping and Failover (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]]
50 -*** [[Flow Configuration (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]]
51 -* [[Failover (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=%22Failover%22||target="blank"]]
52 52  
53 -)))
54 -(((
55 -{{toc/}}
56 -)))
57 -{{/container}}
58 -{{/container}}
33 +)))((({{toc/}}))){{/container}}{{/container}}