Skip to Content
Last modified by Erik Bakker on 2025/04/18 13:54
From version 105.1
edited by Erik Bakker
on 2024/03/12 10:24
Change comment: There is no comment for this version
To version 24.1
edited by eMagiz
on 2022/11/11 09:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Install Docker for Windows
1 +On-premises deployment new runtime architecture
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we will focus on how an on-premises server can be prepared for a eMagiz Deploy agent installation.
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 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -9,95 +9,123 @@
9 9  * Good understanding of eMagiz runtimes in general
10 10  
11 11  == 2. Key concepts ==
12 -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 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 -
12 +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.
13 +
14 +In the below section the specific operating systems and versions are discussed in a sense that the prerequisite installations are described. Once the right installation is done, refer to section 3.5 for the installation of the eMagiz agent that manages the interaction with the eMagiz platform. That agent will download the created docker images that will be deployed in the Docker environment.
15 +
16 16  == 3. On-premises deployments ==
17 +
18 +===3.1 Installation requirements Linux===
17 17  
18 -===3.1 General requirements===
19 -
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
20 +These are the requirements to allow the installation of the eMagiz Docker agent:
21 +* Ensure access to the following URLs is enabled
22 + ** registry.emagiz.com
23 + ** testing.emagiz.com
25 25   ** Preferably the entry should be *.emagiz.com
26 - ** ** Preferably the entry should be *.kpn-dsh.com{{/info}}
25 +* Install latest version of Docker
26 +* Go to the next section around installing the eMagiz agent
27 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
28 +===3.2 Installation requirements Windows Server 2022===
34 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
30 +These are the requirements to allow the installation of the eMagiz Docker agent:
31 +* Ensure access to the following URLs is enabled
32 + ** registry.emagiz.com
33 + ** testing.emagiz.com
34 + ** Preferably the entry should be *.emagiz.com
35 +* Install latest version of Docker
36 +* Validate if WSL 2.0 is properly installed
37 +* Go to the next section around installing the eMagiz agent
42 42  
43 -* When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS.
44 - ** 3.74.209.20:443
45 - ** 3.76.127.155:443
46 - ** 3.74.209.20:8443
47 - ** 3.76.127.155:8443
48 - ** 3.74.209.20:8444
49 - ** 3.76.127.155:8444{{/warning}}
39 + ===3.2 Installation requirements Windows Server 2019 version >1806===
50 50  
51 -===3.2 Installation Windows===
52 -Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported.
41 +These are the requirements to allow the installation of the eMagiz Docker agent:
42 +* Ensure access to the following URLs is enabled
43 + ** registry.emagiz.com
44 + ** testing.emagiz.com
45 + ** Preferably the entry should be *.emagiz.com
46 +* Install latest version of Docker
47 +* Validate if WSL 2.0 is properly installed
48 +* Go to the next section around installing the eMagiz agent
49 +
50 +
51 +===3.3 Installation requirements Windows Server 2019 version 1806===
53 53  
53 +These are the requirements to allow the installation of the eMagiz Docker agent:
54 +* Ensure access to the following URLs is enabled
55 + ** registry.emagiz.com
56 + ** testing.emagiz.com
57 + ** Preferably the entry should be *.emagiz.com
58 +* Enable Hyper-V in Windows Server
59 + ** Go to Server Manager, Manage (top right), enable roles and features, select the desired roles and server selections. In the Features section, enable Hyper-V.
60 + ** Restart windows
61 +* Install Docker Desktop on the Windows Server
62 + ** Please refer to this link: https://www.docker.com/products/docker-desktop/
63 + ** Restart windows
64 +* Update Docker desktop configuration
65 + ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS
66 + ** Restart Docker
67 +* Open Powershell as Administrator
68 + ** Execute "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine
69 + ** Execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
70 + ** Execute curl.exe -L -o ubuntu-2004.appx https://aka.ms/wslubuntu2004
71 + ** Execute Add-AppxPackage .\ubuntu-2004.appx
72 + *** If errors occur, please consult https://learn.microsoft.com/en-us/windows/wsl/install-on-server. Rename the file to a zip, expand it, and add it to the path variable.
73 +* Ubuntu should now be a runnable program (press windows key, type ubuntu)
74 +* Open the ubuntu terminal, and finish the installation.
75 + ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375
76 +* Go to the next section around installing the eMagiz agent
77 +
78 +===3.4 Installation requirements Windows Server 2012 R2 ===
79 +
80 +These are the requirements to allow the installation of the eMagiz Docker agent:
81 +* Ensure access to the following URLs is enabled
82 + ** registry.emagiz.com
83 + ** testing.emagiz.com
84 + ** Preferably the entry should be *.emagiz.com
85 +* Install & enable Hyper-V in Windows Server
86 + ** Go to Server Manager, Manage (top right), enable roles and features, select the desired roles and server selections. In the Features section, enable Hyper-V.
87 + ** Restart windows
88 +* Download a ubuntu server 18.04 (https://releases.ubuntu.com/18.04/ubuntu-18.04.6-live-server-amd64.iso )
89 +* Create a VM in HyperV.
90 + ** For this, choose Generation 1, the amount of memory you want to assign to ubuntu and thus to the containers. Please consider the overhead for memory as well (such as OS).
91 + ** Configure a virtual switch.
92 + ** Add a virtual Hard Disk with proper sizing (e.g. 30 GB)
93 + ** Install an operating system from bootable CD/DVD, ISO file
94 +* Install ubuntu downloaded previously on the VM
95 +* Install docker as per official ubuntu documentation (See https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository) on the VM
96 +* Go to the next section around installing the eMagiz agent
97 +
98 +=== 3.5 eMagiz agent installation agent ===
99 +
100 +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.
54 54  
55 -==== 3.2.1 Docker Installation ====
56 -In powershell with administrative rights, execute the following commands
102 +After installing the agent, validate it runs by checking if a docker container runs on ubuntu.
103 +* wget https://download.docker.com/linux/static/stable/x86_64/docker-20.10.5.tgz
104 +* tar zxvf docker-20.10.5.tgz
105 +* cd docker
106 +* ./docker psg
57 57  
58 -{{code language="cmd"}}
59 -Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/Windows-Containers/Main/helpful_tools/Install-DockerCE/install-docker-ce.ps1" -o install-docker-ce.ps1
60 -.\install-docker-ce.ps1
61 -{{/code}}
62 62  
63 -==== 3.2.2 Check installation ====
109 +== 4. Assignment ==
64 64  
65 -After executing the commands above, the server will restart if required. After the restart, execute the following command
111 +Check out the cheatcheet for Docker command line:
112 +
113 +[[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]]
66 66  
67 -{{code language="cmd"}}
68 -docker ps
69 -{{/code}}
115 +== 5. Key takeaways ==
70 70  
71 -If the command returns that the command cannot be found, please run the following command again.
117 +* 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
118 +* eMagiz has a specific agent that manages the download of that image to the on-premises server
119 +* 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.
72 72  
73 -{{code language="cmd"}}
74 -.\install-docker-ce.ps1
75 -{{/code}}
76 76  
77 -==== 3.2.3 Verify docker functionality ====
78 78  
79 -Execute the following command
123 +== 6. Suggested Additional Readings ==
80 80  
81 -{{code language="cmd"}}
82 -docker ps
83 -{{/code}}
125 +N/A
126 +
127 +== 7. Silent demonstration video ==
84 84  
85 -The result of this call should show the following:
129 +N/A
86 86  
87 -[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-server-windows-installguide--correct-result.png]]
88 -
89 -==== 3.2.4 Install eMagiz Deploy Agent ====
90 -
91 -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"]]
92 -
93 -== 4. Key takeaways ==
94 -
95 -* 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
96 -* eMagiz has a specific agent that manages the download of that image to the on-premises server
97 -* 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.
98 -
99 -== 5. Suggested Additional Readings ==
100 -
101 -* Docker command line cheatsheet: [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]]
102 -
103 103  )))((({{toc/}}))){{/container}}{{/container}}