Changes for page Grouping - Configuration
Last modified by Danniar Firdausy on 2024/09/27 09:11
From version 14.1
edited by Erik Bakker
on 2024/03/01 09:38
on 2024/03/01 09:38
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 - FlowConfiguration1 +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.e bakker1 +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 caneven configure the group to runinan active/passive failovermode when youactivate the multiple runtimesoption on your runtime,andeach separate runtimeis deployed onanother machine. The failover functionalityis not onlyrelevantin casesofservermaintenance. It can alsoassistyou when you wanttoxchangedata with asystemthatallows onlyoneactiveconnection.Shouldthisconnection bebusiness-critical, youcanuse thisfailoverfunctionalitytocreatea passivefailover situationthat will takeover whentheactiveconnection breaksdown (regardlessof theeason).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. 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,53 +15,30 @@ 15 15 16 16 == 2. Key concepts == 17 17 18 -This microlearning describes how t o configure(partsof) your flow(s) to set upthe groupingand,ifneeded,the failoverfunctionalityontheflowlevel.The groupingfunctionalityisrelevantwhenfacedwith maintenanceandoutagesof systemsconnectedto yourmodel.Thefailoverfunctionalitynot only assistsinthat casebutsoallowsyouto have a fallbackoptiononanactiveconnection.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. FlowConfiguration=15 +[[this link>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Microlearnings/Expert%20Level/Solution%20Architecture/expert-solution-architecture-onpremises-server-installguide/|target="_blank"]] 21 21 22 -== 3. 1Grouping ==17 +== 3. Interpreting log on-premise == 23 23 24 - Toconfiguregrouping, weneed to open the flow designer of the flowinCreate. We want todit and enter"Start Editing" mode. Onheinbound component(s) inthe 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 theoptionsaboveare availableinallinbound components. Theonechosen abovemply anillustration of how to configure.{{/info}}23 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]] 29 29 30 - Onceon the"Advanced"tab, youmust definethegroup name. Youcan determinethegroup name ifthisisthefirstflowyouare changing. In allsubsequentflows,you wantto add to themegroup,youmust usethe **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 -When choosing this option, you will see the following pop-up (assuming the machine still needs to be configured). In this pop-up, you must choose between Linux and Windows as OS. Depending on the server OS you previously installed Docker, you must select Linux or Windows. 47 - 48 -[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-os-selection.png]] 49 - 50 -Once you have selected the correct OS for you, the next step is to press "Save." This action will lead you to another pop-up showing the command that needs to be executed (with administrator rights) on the host machine. This way, the deploy agent is activated on the host machine. 51 -== 3.3 Failover Infra == 52 -[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent-command.png]] 53 - 54 -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. 55 - 56 56 == 4. Key takeaways == 57 57 58 -* 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 59 59 60 -== 5. Suggested Additional Readings ==33 +== 6. Suggested Additional Readings == 61 61 62 -There are no suggested additional readings for this microlearning.))) 63 -((( 64 -{{toc/}} 65 -))) 66 -{{/container}} 67 -{{/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}}