Skip to Content
Last modified by Erik Bakker on 2025/04/18 13:54
From version 4.1
edited by eMagiz
on 2022/06/24 15:00
Change comment: There is no comment for this version
To version 15.1
edited by Erik Bakker
on 2022/10/31 15:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,11 +1,8 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 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  
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
... ... @@ -16,18 +16,32 @@
16 16  
17 17  == 3. On-premises deployments ==
18 18  
19 -===3.1 Installation requirements===
20 -Below the list of requirements for an on-premises deployment
16 +===3.1 Installation requirements Windows Server 2019 version 1806===
21 21  
22 -* Windows Server or Linux Server
23 -* Installed Docker software
24 -* Server connected to the internet whereby the firewall doesn't prevent data traffic going outwards to the Internet
25 - ** In case there are outgoing firewall rules, eMagiz can provide the specific URL's and port numbers in order to update the firewall
26 -* Sufficient resources inline 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"]]
18 +Below the installation step for this version of Windows
19 +
20 +* Enable Hyper-V in Windows Server
21 + ** 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.
22 + ** Restart windows
23 +* Install Docker Desktop on the Windows Server
24 + ** Please refer to this link: https://www.docker.com/products/docker-desktop/
25 + ** Restart windows
26 +* Update Docker desktop configuration
27 + ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS
28 + ** Restart Docker
29 +* Open Powershell as Administrator
30 + ** Execute "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine
31 + ** Execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
32 + ** Execute curl.exe -L -o ubuntu-2004.appx https://aka.ms/wslubuntu2004
33 + ** Execute Add-AppxPackage .\ubuntu-2004.appx
34 + *** 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.
35 +* Ubuntu should now be a runnable program (press windows key, type ubuntu)
36 +* Open the ubuntu terminal, and finish the installation.
37 + ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375
27 27  
28 28  === 3.2 Installation agent ===
29 29  
30 -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.
41 +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.
31 31  
32 32  === 3.3 Cloud architecture for API Gateway ===
33 33  
... ... @@ -35,24 +35,22 @@
35 35  
36 36  == 4. Assignment ==
37 37  
38 -There is no specific assignment for this microlearning.
49 +Check out the cheatcheet for Docker command line:
50 +
51 +[[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]]
39 39  
40 40  == 5. Key takeaways ==
41 41  
42 -* eMagiz will help to determine the needed memory via the Design Architecture page.
43 -* eMagiz works with pre-determined sizes that are represented via an S, M, L, XL structure. Every size has a certain amount of memory available
44 -* When you exceed such a threshold you should upgrade (or downgrade) your memory in consultation with your partner manager
45 -* Overhead for OS and support functionality (auto-healing, alerting, monitoring) needs to be taken into account
46 -* Calculating memory can be challenging. Always confer with others before taking action
47 -* You can compare your calculations with the calculations of eMagiz
48 -* The calculations and logic described below are applicable for the Messaging, API Gateway and Event Streaming pattern
55 +* 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
56 +* eMagiz has a specific agent that manages the download of that image to the on-premises server
57 +* 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.
49 49  
50 50  
51 51  
52 52  == 6. Suggested Additional Readings ==
53 53  
54 -If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
55 -
63 +N/A
64 +
56 56  == 7. Silent demonstration video ==
57 57  
58 58  N/A