Wiki source code of eMagiz Deploy agent

Version 12.1 by Erik Bakker on 2024/02/09 14:04

Hide last authors
Erik Bakker 10.1 1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
Erik Bakker 12.1 4 eMagiz runtimes can run on local, on-premises servers. The main reason is that some systems are only accessible within the client's infrastructure. In such a scenario, the on-premises server must have a Docker installation before you can communicate between your on-premise server and eMagiz.
eMagiz 1.1 5
6 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7
8 == 1. Prerequisites ==
9
10 * Intermediate knowledge of the eMagiz platform
11
12 == 2. Key concepts ==
13
Erik Bakker 12.1 14 This microlearning describes how the eMagiz Deploy agent is installed on the on-premises server where an eMagiz runtime should run. 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-linux-installguide.WebHome||target="blank"]] for **Linux** and in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-windows-installguide.WebHome||target="blank"]] for **Windows**.
eMagiz 1.1 15
eMagiz 6.1 16 == 3. eMagiz Deploy agent installation ==
eMagiz 1.1 17
Erik Bakker 12.1 18 eMagiz needs to install a specific agent in the Docker instance that allows the downloading of runtime images that need to be installed on the Docker instance. The exact command to run inside the Docker instance is specific for the machine configured inside eMagiz Design & Deploy Architectures. It can be found inside the eMagiz iPaaS portal under Deploy Architecture. The runtime connector has a right-click option called Deploy Agent.
Erik Bakker 11.1 19
Erik Bakker 12.1 20 [[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
eMagiz 1.1 21
Erik Bakker 12.1 22 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.
eMagiz 1.1 23
Erik Bakker 12.1 24 [[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-os-selection.png]]
25
26 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.
27
28 [[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent-command.png]]
29
30 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.
31
eMagiz 1.1 32 == 4. Key takeaways ==
33
eMagiz 4.1 34 * The eMagiz Docker agent needs to be installed to allow runtime to be installed on the on-premises server
eMagiz 1.1 35
eMagiz 8.1 36 == 5. Suggested Additional Readings ==
eMagiz 1.1 37
Erik Bakker 12.1 38 There are no suggested additional readings for this microlearning.)))
Erik Bakker 10.1 39 (((
40 {{toc/}}
41 )))
42 {{/container}}
43 {{/container}}