Changes for page Failover - Deploy Possibilities
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.77
edited by dfirdausy
on 2024/09/25 20:22
on 2024/09/25 20:22
Change comment:
There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2024/02/08 16:39
on 2024/02/08 16:39
Change comment:
There is no comment for this version
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - Setting up Failover-DeployPhase1 +eMagiz Deploy agent - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Main.eMagiz Academy.Microlearnings.Intermediate Level. Groupingand Failover.WebHome1 +Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,47 +1,37 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 +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. 4 4 5 -In the previous microlearning, we discussed what needs to be done in the Create phase to enable failover for systems that are configured to have them in the Design phase. Next to that, we also discussed that setting up this failover functionality in your model requires you to execute some steps in your Design, Create, and lastly Deploy phase. Picking up from what we have toggled in the Create phase, in this microlearning, we will focus on the steps and configurations that you have to make in the Deploy phase to activate the active/passive failover functionality. 6 - 7 7 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 8 8 9 9 == 1. Prerequisites == 10 10 11 -* Intermediate knowledge of the eMagiz platform .10 +* Intermediate knowledge of the eMagiz platform 12 12 13 13 == 2. Key concepts == 14 14 15 -This microlearning describes whatconfigurationthatyouwillhavetodoin theDeployphase,basedonwhatyouhaveconfiguredin theDesignandCreatephase,toenable failoverforsystemsconnectingwith yourmodel. Thegrouping andfailoverfunctionalityis relevantwhenfacedwith maintenanceandoutagesof systemsconnectedtoyourmodel.Thefailoverfunctionalityassistsin thatcaseand allowsyouto havea fallback optiononan activeconnection.14 +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-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. 16 16 17 -== 3. Deploy PhaseConfiguration ==16 +== 3. eMagiz Deploy agent installation == 18 18 19 - ==3.1Deploy Architecture==18 +eMagiz needs to install a specific agent in the Docker instance that allows to download runtime images that need 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. In case the command is presented it means that this machine is not yet equipped with the eMagiz Deploy agent. The command can be executed inside the Linux command prompt on the on-premises server. 20 20 21 - Afterfinishingup your configurationintheCreatephase,you can thenmove toyour Deploy>Architecture.Here,youwillseethenew routercontainers,which wehaveseenintheDesign>Architecture, tobeaddedtoyour externalmachines.Whenyoupress"Start Editing"inthis page,andthen press "Applytoenvironment", you will befacedwithapop-uppagethatinforms you thattheserouter containers will be created forthisspecific environmentasshownin thescreenshotbelow.20 +Once the agent is installed, eMagiz can manage the machine to deploy new runtimes and or update runtimes as needed. Also the container runtime can be controlled with start, stop, et 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. 22 22 23 -[[image:Main.Images.Microlearning.WebHome@ grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-router-containers.png]]22 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]] 24 24 25 -Once you have applied the changes, when you go to the "Details" of each of those machines via right-clicking them, then you can find and set for each failover runtime the preferred machine to be the leader. As an example shown in the screenshot below, there are two runtimes that are enabled for failover and you can select whether that runtime running in that "External 01" machine is the preferred leader. Another option is to set the runtime that you select as the backup, or reset it back to "None" if you want. 26 - 27 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-failover-preference.png]] 28 - 29 -When you have made your decision, and assuming that your machines are already deployed and running, then you can move to the other page discussed in the next section. 30 - 31 -== 3.2 Deployment Plan == 32 - 33 -== 3.3 Deploy Release == 34 - 35 35 == 4. Key takeaways == 36 36 37 - ...26 +* The eMagiz Docker agent needs to be installed to allow runtime to be installed on the on-premises server 38 38 39 39 == 5. Suggested Additional Readings == 40 40 41 - If youareinterested inthis topic and wantmoreinformation, pleasereadthe help text providedby eMagiz andcheckout theselinks:30 +No suggested additional readings for this microlearning. 42 42 43 - * [[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"]]32 + 44 44 ))) 34 + 45 45 ((( 46 46 {{toc/}} 47 47 )))