Skip to Content
Last modified by Erik Bakker on 2026/01/30 10:56
From version 11.1
edited by eMagiz
on 2022/10/19 08:46
Change comment: There is no comment for this version
To version 137.1
edited by Erik Bakker
on 2024/11/29 08:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -On-premises deployment new runtime architecture
1 +Install Docker for Windows
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,11 +1,8 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we will focus on how the installation requirements for on-premises deployments of eMagiz runtimes that are part of the new runtime architecture. The new runtime architecture uses a containerized approach to deploy runtimes.
3 -
2 +In eMagiz's current runtime architecture, Docker technology is utilized to deploy runtimes efficiently. eMagiz provides specific runtime images that can be deployed within dockerized environments. This section outlines the steps needed to prepare a Windows server for the installation of the eMagiz Deploy Agent, which is responsible for downloading these images from the eMagiz infrastructure.
3 +
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -* Last update: June 24th 2021
7 -* Required reading time: 10 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  
11 11  * Advanced knowledge of the eMagiz platform
... ... @@ -12,54 +12,162 @@
12 12  * Good understanding of eMagiz runtimes in general
13 13  
14 14  == 2. Key concepts ==
15 -In the new runtime architecture of eMagiz, Docker technology is used to deploy runtimes. eMagiz creates specific runtime images that contain the eMagiz runtime, and can be deployed in dockerized envirionments
16 -
12 +In the current runtime architecture of eMagiz, Docker technology is used to deploy runtimes. eMagiz creates specific runtime images that contain the eMagiz runtime, and can be deployed in dockerized environments.
13 +
14 +In the below section the Windows variant is described in terms of how to prepare the server to allow the [[eMagiz Deploy Agent>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]] to be installed. That agent allows to download images from the eMagiz infrastructure.
15 +
17 17  == 3. On-premises deployments ==
18 18  
19 -===3.1 Installation requirements===
20 -Below the list of requirements for an on-premises deployment
18 +===3.1 General requirements===
21 21  
22 -* Windows Server or Linux Server
23 - ** Windows Server requires installation of the Linux subsystem for Windows. Please refer to this link: https://learn.microsoft.com/en-us/windows/wsl/install-on-server
24 -* Installed Docker software - latest version
25 -* Optional: Install Docker Desktop for Windows
26 - ** See also [[Install guide Docker>>https://docs.docker.com/desktop/install/windows-install/]]
27 -* Docker software installed requires use of the LinuxEngine (valid for Windows based Docker engine installations)
28 - ** Use command line option to switch to the option"C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine
29 -* Server connected to the internet whereby the firewall doesn't prevent data traffic going outwards to the Internet
30 - ** In case there are outgoing firewall rules, the following URLs need to be made available
31 - *** https://testing.emagiz.com
32 - *** https://registry.emagiz.com
33 -* Sufficient resources in line with the requirements of the eMagiz runtimes. See this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory.WebHome||target="blank"]]
20 +{{info}}
21 +* Standard configuration to ensure that communication between your server and eMagiz to ensure communication.
22 + ** registry.emagiz.com:443
23 + ** controlplane.emagiz.com:8000
24 + ** controltower.kpn-dsh.com:443
25 + ** Preferably the entry should be *.emagiz.com
26 + ** Preferably the entry should be *.kpn-dsh.com{{/info}}
27 +
28 +{{warning}}
29 +* In case of a very strict firewall configuration, additional configuration is needed to communicate to the eMagiz infrastructure.
30 + ** controltower.emagiz.com:443
31 + ** controltower.kpn-dsh.com:443
32 + ** controlbus.emagiz.com:443
33 + ** controlplane.emagiz.com:443
34 +
35 +* When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS.
36 + ** 35.158.46.28:443
37 + ** 3.74.190.88:443
38 + ** 35.158.46.28:8443
39 + ** 3.74.190.88:8443
40 + ** 35.158.46.28:8444
41 + ** 3.74.190.88:8444
42 + ** 18.199.123.240
43 + ** 18.184.211.189
44 + ** 3.123.136.31
45 +
46 +* When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS.
47 + ** 3.74.209.20:443
48 + ** 3.76.127.155:443
49 + ** 3.74.209.20:8443
50 + ** 3.76.127.155:8443
51 + ** 3.74.209.20:8444
52 + ** 3.76.127.155:8444
53 + ** 18.199.123.240
54 + ** 18.184.211.189
55 + ** 3.123.136.31{{/warning}}
56 +
57 +===3.2 Installation Windows===
58 +Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported.
59 +
60 +
61 +==== 3.2.1 Docker Installation ====
62 +To install or update docker on your machine, execute the following commands in powershell with administrative rights:
63 +
64 +{{code language="cmd"}}
65 +Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Install-update-docker/install-update-docker.ps1" -o install-update-docker-ce.ps1
66 +.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
67 +{{/code}}
68 +
69 +{{info}}It is advised to use Docker version 24.0.7 as this is the version being used in the latest eMagiz cloud template. We advise to align the on-premise Docker version and update it according to the release notes of the [[Cloud templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
70 +{{/info}}
71 +
72 +==== 3.2.2 Customization ====
73 +
74 +After installing Docker you have the option to stick with the standard configuration of Docker or you can opt to alter some specific settings. Settings that can be of particular interest are the setting that defines the IP address range your Docker installation will use to run the containers and the setting that defines where to store data (i.e. containers and images). To check the full list of compatible configuration options for Windows you can check: [[Configure Docker in Windows>>https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/configure-docker-daemon||target="blank"]].
75 +
76 +{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
77 +
78 +===== 3.2.2.1 IP address range =====
34 34  
35 -=== 3.2 Installation agent ===
80 +Below you can find the code necessary to configure a different IP address range.
81 +
82 +{{code language="cmd"}}
83 +cd C:\ProgramData\Docker\config\daemon.json
84 +#Add following lines
85 +{"fixed-cidr": "<ip-address>"}
86 +{{/code}}
36 36  
37 -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 or is available upon request. Once that agent is installed, the image that is generated for every eMagiz release can be downloaded and installed in the Docker instance.
88 +===== 3.2.2.2 Data location =====
38 38  
39 -=== 3.3 Cloud architecture for API Gateway ===
90 +Below you can find an example of switching from the default C directory ({{code language="cmd"}}c:\programdata\docker{{/code}}) to the D directory to store data related to Docker. Based on your internal configuration you can choose the best suitable variant if that is needed. To do so you can add the following attribute to the Docker daemon file:
91 +
92 +{{code language="cmd"}}
93 +cd C:\ProgramData\Docker\config\daemon.json
94 +#Add following lines
95 +{
96 + "data-root": "d:\\docker"
97 +}
98 +{{/code}}
40 40  
41 -[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-install-runtime-images.png]]
100 +{{warning}}Note that when you want to create multiple customizations to your configuration the result in the daemon.json file should be a **valid** JSON structure{{/warning}}
42 42  
43 -== 4. Assignment ==
102 +==== 3.2.3 Check installation ====
44 44  
45 -Check out the cheatcheet for Docker command line:
46 -
47 -[[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]]
104 +After executing the commands above, the server will restart if required. After the restart, execute the following command
48 48  
49 -== 5. Key takeaways ==
106 +{{code language="cmd"}}
107 +docker ps
108 +{{/code}}
50 50  
51 -* eMagiz uses runtime images to deploy emagiz runtime on dockerized environments. The runtime image holds all the information and components required to run the runtime
52 -* eMagiz has a specific agent that manages the download of that image to the on-premises server
53 -* The firewall of the on-premises environment should allow outgoing traffic without any restriction. In case that is not desirable, eMagiz can provide the addresses and ports needed to setup the right firewall rules.
110 +If the command returns that the command cannot be found, please run the following command again.
54 54  
112 +{{code language="cmd"}}
113 +.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
114 +{{/code}}
55 55  
116 +==== 3.2.3 Verify docker functionality ====
56 56  
57 -== 6. Suggested Additional Readings ==
118 +Execute the following command
58 58  
59 -N/A
60 -
61 -== 7. Silent demonstration video ==
120 +{{code language="cmd"}}
121 +docker ps
122 +{{/code}}
62 62  
63 -N/A
124 +The result of this call should show the following:
64 64  
126 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-server-windows-installguide--correct-result.png]]
127 +
128 +==== 3.2.4 Install eMagiz Deploy Agent ====
129 +
130 +Install the eMagiz Deploy agent as can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]]
131 +
132 +===3.3 Uninstall Docker===
133 +To uninstall docker from your machine, execute the following commands in powershell with administrative rights:
134 +
135 +{{code language="cmd"}}
136 +Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1
137 +{{/code}}
138 +
139 +Example usage:
140 +
141 +{{code language="cmd"}}
142 +.\uninstall-docker-ce.ps1
143 +{{/code}}
144 +
145 +== 4. Key takeaways ==
146 +
147 +* eMagiz uses runtime images to deploy emagiz runtime on dockerized environments. The runtime image holds all the information and components required to run the runtime
148 +* eMagiz has a specific agent that manages the download of that image to the on-premises server
149 +* The firewall of the on-premises environment should allow outgoing traffic without any restriction. In case that is not desirable, eMagiz can provide the addresses and ports needed to setup the right firewall rules.
150 +
151 +== 5. Suggested Additional Readings ==
152 +
153 +* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
154 +** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]
155 +* [[Release Information (Menu)>>doc:Main.Release Information.WebHome||target="blank"]]
156 +** [[Environment Templates (Navigation)>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
157 +* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
158 +** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]]
159 +*** [[Interpret on-premise logging (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-interpret-on-premise-logging.WebHome||target="blank"]]
160 +*** [[eMagiz Deploy agent (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]]
161 +* [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]]
162 +** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.WebHome||target="blank"]]
163 +*** [[Impact of Runtime Image Upgrades (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.advanced-lifecycle-management-impact-of-runtime-image-upgrades.WebHome||target="blank"]]
164 +* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]]
165 +** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]]
166 +*** [[Install Docker for Linux (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]]
167 +* [[Install Docker (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=install+docker||target="blank"]]
168 +* Docker command line cheatsheet: [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]]
169 +
65 65  )))((({{toc/}}))){{/container}}{{/container}}