Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.78
edited by dfirdausy
on 2024/09/25 20:33
Change comment: There is no comment for this version
To version 1.1
edited by eMagiz
on 2023/02/07 12:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Setting up Failover - Deploy Phase
1 +intermediate-runtime-management-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.eMagiz
Content
... ... @@ -1,51 +1,39 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
1 +{{container}}{{container layoutStyle="columns"}}(((
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.
3 +In some cases, the complete stack trace must be logged when something goes wrong on runtime. In eMagiz, only the top-level information is shown, and sometimes the entire stack trace. When this particular runtime runs on-premises, you can see the complete logging on the runtime level. In this microlearning, we will learn how to find the log and look through the log to find the corresponding error and subsequently analyze that error.
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 what configuration that you will have to do in the Deploy phase, based on what you have configured in the Design and Create phase, to enable failover for systems connecting with your model. The grouping and failover 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.
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 on
16 16  
17 -== 3. Deploy Phase Configuration ==
15 +OnfigfueMain.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide
18 18  
19 -== 3.1 Deploy Architecture ==
17 +== 3. Interpreting log on-premise ==
20 20  
21 -After finishing up your configuration in the Create phase, you can then move to your Deploy>Architecture. Here, you will see the new router containers, which we have seen in the Design>Architecture, to be added to your external machines. When you press "Start Editing" in this page, and then press "Apply to environment", you will be faced with a pop-up page that informs you that these router containers will be created for this specific environment as shown in the screenshot below.
19 +=== 3.7 eMagiz Docker agent installation ===
22 22  
23 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-router-containers.png]]
21 +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.
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.
23 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]]
26 26  
27 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-failover-preference.png]]
25 +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.
28 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 -If this is the first time that you configure your failover setup, then the next step in Deploy is to check the Deployment Plan. Here, you can add a deployment step called "Balance failover", which, when executed, will trigger the failover container(s) to be running on its preferred machine as you previously configured them in Deploy>Architecture.
34 -
35 -== 3.3 Deploy Release ==
36 -
37 37  == 4. Key takeaways ==
38 38  
39 -...
29 +* The karaf.log can be found within the folder called log under the folder data
30 +* You can search the log with the help of tools such as Notepad++
31 +* By looking at the timestamp in the eMagiz Manage Log, you can run a focused search
40 40  
41 -== 5. Suggested Additional Readings ==
33 +== 6. Suggested Additional Readings ==
42 42  
43 -If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links:
35 +No suggested additional readings for this microlearning.
44 44  
45 -* [[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"]]
46 -)))
47 -(((
48 -{{toc/}}
49 -)))
50 -{{/container}}
51 -{{/container}}
37 +* [[Container commands on containers>>https://docs.docker.com/engine/reference/commandline/ps/||target="blank"]]
38 +* [[Logging commands on containers>>https://docs.docker.com/engine/reference/commandline/logs/||target="blank"]]
39 +)))((({{toc/}}))){{/container}}{{/container}}