Skip to Content
Last modified by dfirdausy on 2024/09/27 09:18
From version 13.1
edited by Erik Bakker
on 2024/03/01 09:05
Change comment: There is no comment for this version
To version 34.1
edited by BoukeReitsma
on 2024/03/15 09:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Flow Configuration
1 +Deploy Possibilities
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.BoukeReitsma
Content
... ... @@ -1,8 +1,12 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 -eMagiz runtimes can run on local, on-premises servers. The main reason is that some systems are only accessible within the client's infrastructure. In such a scenario, the on-premises server must have a Docker installation before you can communicate between your on-premise server and eMagiz.
4 +eMagiz flows, or more specifically, the flow's inbound component(s), can be grouped. How to configure 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.
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 not only relevant in cases of server maintenance. It can also 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).
7 +
8 +In this microlearning, we will focus on configuring the deployment plan to control various inbound compoments in a normal and in a failover configuration.
9 +
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 8  == 1. Prerequisites ==
... ... @@ -11,29 +11,32 @@
11 11  
12 12  == 2. Key concepts ==
13 13  
14 -This microlearning describes how the eMagiz Deploy agent is installed on the on-premises server where an eMagiz runtime should run. 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-linux-installguide.WebHome||target="blank"]] for **Linux** and in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-windows-installguide.WebHome||target="blank"]] for **Windows**.
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 in that case and allows you to have a fallback option on an active connection.
15 15  
16 -== 3. eMagiz Deploy agent installation ==
20 +== 3. Group Deployment Step ==
17 17  
18 -eMagiz needs to install a specific agent in the Docker instance that allows the downloading of runtime images that need to be installed on the Docker instance. The exact command to run inside the Docker instance is specific for the machine configured inside eMagiz Design & Deploy Architectures. It can be found inside the eMagiz iPaaS portal under Deploy Architecture. The runtime connector has a right-click option called Deploy Agent.
22 +To configure a Group deployment step, you need to add a new deployment step and choose Step type "Group". To configure the step more information is required. A container should be chosen 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. For a "Group" deployment step the options are to start or to stop the inbound components within the groupname. Optionally, a description can be added.
19 19  
20 -[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
24 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-group-deployment-step.png]]
21 21  
22 -When choosing this option, you will see the following pop-up (assuming the machine still needs to be configured). In this pop-up, you must choose between Linux and Windows as OS. Depending on the server OS you previously installed Docker, you must select Linux or Windows.
26 +== 4. Failover Deployment Step ==
23 23  
24 -[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-os-selection.png]]
28 +The configuration of a failover deployment step is similar as for the Group deployment step. The only difference is the action you can activate. The stop group actions make the inbounds of the currently selected container stop. If this group is the leader of the failover group. It will deactivate this group and start orignal follower group. However, it disables failover. Therefore, from this point were are running in a dubble setup in which we have single node leaders.
25 25  
26 -Once you have selected the correct OS for you, the next step is to press "Save." This action will lead you to another pop-up showing the command that needs to be executed (with administrator rights) on the host machine. This way, the deploy agent is activated on the host machine.
30 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.png]]
27 27  
28 -[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent-command.png]]
32 +The start group step with failover will activate the current container as the leader of the failover setup. Therefore, resembling group names on other containers will become the followers. If these flows were running, they will be stopped.
29 29  
30 -Once the agent is installed, eMagiz can manage the machine to deploy new runtimes or update runtimes as needed. Also, the container runtime can be controlled with start, stop, and reset commands. Please consult this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-interpret-on-premise-logging.WebHome||target="blank"]] to inspect the on-premises runtime logs.
34 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-failover-deployment-step.png]]
31 31  
32 -== 4. Key takeaways ==
36 +== 5. Key takeaways ==
33 33  
34 -* The eMagiz Docker agent needs to be installed to allow runtime to be installed on the on-premises server
38 +* Grouping is beneficial when external systems go through maintenance or downtime.
39 +* 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
40 +* The role naming in both grouping and failover is crucial. The group name needs to match **exactly** to make it work.
41 +* You can control group and failover steps from the deployment plan
35 35  
36 -== 5. Suggested Additional Readings ==
43 +== 6. Suggested Additional Readings ==
37 37  
38 38  There are no suggested additional readings for this microlearning.)))
39 39  (((