Changes for page Grouping - Deploy Possibilities

Summary

• Page properties (4 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Deploy Possibilities
	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.BoukeReitsma
	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. 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.
	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 deployment plan to control various inbound compoments in a normal and in a 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,36 +15,30 @@
15	15
16	16	== 2. Key concepts ==
17	17
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.
	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. Group Deployment Step ==
	15	+OnfigfueMain.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide
21	21
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.
	17	+== 3. Interpreting log on-premise ==
23	23
24		-[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-group-deployment-step.png]]
	19	+=== 3.7 eMagiz Docker agent installation ===
25	25
26		-== 4. Failover Deployment Step ==
	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		-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.
	23	+[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]]
29	29
30		-[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.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.
31	31
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.
	27	+== 4. Key takeaways ==
33	33
34		-[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-failover-deployment-step.png]]
	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
35	35
36		-== 5. Key takeaways ==
37		-
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
42		-
43	43	== 6. Suggested Additional Readings ==
44	44
45		-There are no suggested additional readings for this microlearning.)))
46		-(((
47		-{{toc/}}
48		-)))
49		-{{/container}}
50		-{{/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}}