Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 16.1
edited by Erik Bakker
on 2024/03/01 11:59
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 -Flow Configuration
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.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -1,12 +1,7 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
4 -eMagiz flows, or more specifically, the flow's inbound component(s), can be grouped. The effect is that you can later in [[Deploy>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]], control them as one entity. This 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 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).
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.
7 7  
8 -In this microlearning, we will focus on configuring the flow to group various inbound components and configure the flow (including the infra) if you want to activate the active/passive failover configuration.
9 -
10 10  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
11 11  
12 12  == 1. Prerequisites ==
... ... @@ -15,62 +15,30 @@
15 15  
16 16  == 2. Key concepts ==
17 17  
18 -This microlearning describes how to configure (parts of) your flow(s) to set up the grouping and, if needed, the failover functionality on the flow level. The grouping functionality is relevant when faced with maintenance and outages of systems connected to your model. The failover functionality not only assists in that case but also 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
19 19  
20 -== 3. Flow Configuration ==
15 +OnfigfueMain.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide
21 21  
22 -== 3.1 Grouping ==
17 +== 3. Interpreting log on-premise ==
23 23  
24 -To configure grouping, we need to open the flow designer of the flow in Create. We want to edit and enter "Start Editing" mode. On the inbound component(s) in the flow, we now have an "Advanced" tab that allows you to configure the grouping information.
19 +=== 3.7 eMagiz Docker agent installation ===
25 25  
26 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-starting-point.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.
27 27  
28 -{{info}}Note that the options above are available in all inbound components. The one chosen above is simply an illustration of how to configure.{{/info}}
23 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]]
29 29  
30 -Once on the "Advanced" tab, you must define the group name. You can determine the group name if this is the first flow you are changing. In all subsequent flows, you want to add to the same group, you must use the **same** group name.
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.
31 31  
32 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-define-group-name.png]]
33 -
34 -Once filled in, ensure that the auto startup configuration is set to Yes to ensure that, on default, all flows within the group start up when the container is started.
35 -
36 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-define-auto-startup.png]]
37 -
38 -Within a runtime context, you can add multiple groups that can be stopped and started separately from each other. In this example, we would also like to have a group for our exits to stop them if the connecting system undergoes maintenance or is down to store the messages in the queue.
39 -
40 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-starting-point-exit.png]]
41 -
42 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-other-group.png]]
43 -
44 -== 3.2 Failover ==
45 -
46 -In case you want to expand the grouping functionality to include a active/passive failover component you need to change the settings on the inbound component. Apart from specifying the name of the group you need to configure the auto-startup option on "No" so the failover configuration can take the correct actions in all situations.
47 -
48 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-failover-example-group.png]]
49 -
50 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-failover-other-group.png]]
51 -
52 -{{info}}Note that each group within a single runtime that you want to treat differently needs to have a **unique** name.{{/info}}
53 -
54 -== 3.3 Failover Infra ==
55 -
56 -The configuration of the infra flow of the runtime for which you want to configure the failover is detailed and only works in case you configured all support objects correctly. Although we explain the various steps here in the documentation we advise to utilize the store item that we created for this that will guide you in setting this up correctly.
57 -
58 -The configuration consists of at least three seperate support objects. Two of them are needed once (infinispan cache manager and clustered lock registry) were the other is needed per unique group you have defined within the context of your runtime. So if you have two unique group names within the runtime you need two leader initiator support objects.
59 -
60 -Given this let us first look at the infinispan cache manager
61 -[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent-command.png]]
62 -
63 -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.
64 -
65 65  == 4. Key takeaways ==
66 66  
67 -* The eMagiz Docker agent needs to be installed to allow runtime to be installed on the on-premises server
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
68 68  
69 -== 5. Suggested Additional Readings ==
33 +== 6. Suggested Additional Readings ==
70 70  
71 -There are no suggested additional readings for this microlearning.)))
72 -(((
73 -{{toc/}}
74 -)))
75 -{{/container}}
76 -{{/container}}
35 +No suggested additional readings for this microlearning.
36 +
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}}