Changes for page Failover - Deploy Possibilities
Last modified by Erik Bakker on 2024/09/27 14:07
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - SettingupFailover- CreatePhase1 +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.eMagiz - Content
-
... ... @@ -1,59 +1,33 @@ 1 -{{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 1 +{{container}}{{container layoutStyle="columns"}}((( 4 4 5 - In thepreviousmicrolearning, wediscussedwhatsituationthat failovermode will be beneficialas well as the settings that need tobe configuredin theDesignphase.Next to that,wealsodiscussedthat settingupthisfailoverfunctionalityin your modelrequiresyouto firstexecutesomesteps inyourDesign, Create,andlastly Deploy phase.Picking up fromwhatwe have discussedpreviously in theDesignphase, in this microlearning,wewill focus onconfiguringyour setup intheCreatephaseif youwanttoactivatethe active/passive failover configuration.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. 6 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 .9 +* Intermediate knowledge of the eMagiz platform 12 12 13 13 == 2. Key concepts == 14 14 15 -This microlearning describes whatconfigurationthatyouwillhavetodoin theCreate phase,basedonwhatyouhaveconfiguredin theDesignphase,toenablefailoverforsystems connectingwithyourmodel. Thegrouping andfailoverfunctionalityis relevantwhenfacedwith maintenanceandoutagesof systemsconnectedtoyourmodel.Thefailoverfunctionality assistsin that caseand allowsyouto have a fallbackoption onan activeconnection.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"]]. 16 16 17 -== 3. Create Phase Configuration == 18 18 19 -== 3. 1Settings ==16 +== 3. eMagiz Deploy agent installation == 20 20 21 -After finishing up your configuration in the Design phase, you can then go to the Settings page on the top right corner of the Create phase. In this page, under the "Failover systems" tab in the "Transfer settings from design" section, you will find the system connector(s) that you can transfer the failover settings from Design. Please check the screenshot below as an example. 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. 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. 19 + 20 +Once the agent is installed, eMagiz can manage the machine to deploy new runtime 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-create-phase-create-settings.png]]22 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]] 24 24 25 -By pressing the "Transfer failover" button, eMagiz will regenerate the connector infra flow of that system as well as update the exit and entry flows connected to that system with the required settings. We will discuss these required settings and what components are affected in the following section. 26 - 27 -== 3.2 Flow Configurations == 28 - 29 -As mentioned just now, by pressing that button in Create>Settings, eMagiz will configure the correct settings for you, so then you do not have to configure them manually by yourself. 30 - 31 31 == 4. Key takeaways == 32 32 33 -* Grouping is beneficial when external systems go through maintenance or downtime. 34 -* 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. 35 -* The role naming in both grouping and failover is crucial. The whole name needs to be matched fully to make it work. 36 -* For the infra configuration of the failover setup, we have a store item that you can use. 26 +* The eMagiz Docker agent needs to be installed to allow runtime to be installed on the on-premises server 37 37 38 -== 5. Suggested Additional Readings ==28 +== 6. Suggested Additional Readings == 39 39 40 - If youareinterested inthis topic and wantmoreinformation, pleasereadthe help text providedby eMagiz andcheckout theselinks:30 +No suggested additional readings for this microlearning. 41 41 42 -* [[eMagiz Store (Menu)>>doc:Main.eMagiz Store.WebHome||target="blank"]] 43 -** [[Accelerators (Navigation)>>doc:Main.eMagiz Store.Accelerators.WebHome||target="blank"]] 44 -*** [[Active/Passive Failover (Explanation)>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.WebHome||target="blank"]] 45 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] 46 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] 47 -*** [[Support objects - Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] 48 -*** [[Promote flows to deploy (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-promote-flows-to-deploy||target="blank"]] 49 -* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]] 50 -** [[Grouping and Failover (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]] 51 -*** [[Deploy Possibilities (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]] 52 -** [[eMagiz Cloud Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]] 53 -* [[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"]] 54 -))) 55 -((( 56 -{{toc/}} 57 -))) 58 -{{/container}} 59 -{{/container}} 32 + 33 +)))((({{toc/}}))){{/container}}{{/container}}