Wiki source code of On-premises deployment new runtime architecture
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | |||
| 4 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 5 | |||
| 6 | == 1. Prerequisites == | ||
| 7 | |||
| 8 | * Advanced knowledge of the eMagiz platform | ||
| 9 | * Good understanding of eMagiz runtimes in general | ||
| 10 | |||
| 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 envirionments | ||
| 13 | |||
| 14 | == 3. On-premises deployments == | ||
| 15 | |||
| 16 | ===3.1 Installation requirements Linux=== | ||
| 17 | |||
| 18 | * Ensure access to the following URLs is enabled | ||
| 19 | ** registry.emagiz.com | ||
| 20 | ** testing.emagiz.com | ||
| 21 | ** Preferably the entry should be *.emagiz.com | ||
| 22 | * Install latest version of Docker | ||
| 23 | |||
| 24 | ===3.2 Installation requirements Windows Server 2022=== | ||
| 25 | |||
| 26 | * Ensure access to the following URLs is enabled | ||
| 27 | ** registry.emagiz.com | ||
| 28 | ** testing.emagiz.com | ||
| 29 | ** Preferably the entry should be *.emagiz.com | ||
| 30 | * Install latest version of Docker | ||
| 31 | * Validate if WSL 2.0 is properly installed | ||
| 32 | |||
| 33 | ===3.3 Installation requirements Windows Server 2019 version 1806=== | ||
| 34 | |||
| 35 | Below the installation step for this version of Windows | ||
| 36 | |||
| 37 | * Ensure access to the following URLs is enabled | ||
| 38 | ** registry.emagiz.com | ||
| 39 | ** testing.emagiz.com | ||
| 40 | ** Preferably the entry should be *.emagiz.com | ||
| 41 | * Enable Hyper-V in Windows Server | ||
| 42 | ** 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. | ||
| 43 | ** Restart windows | ||
| 44 | * Install Docker Desktop on the Windows Server | ||
| 45 | ** Please refer to this link: https://www.docker.com/products/docker-desktop/ | ||
| 46 | ** Restart windows | ||
| 47 | * Update Docker desktop configuration | ||
| 48 | ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS | ||
| 49 | ** Restart Docker | ||
| 50 | * Open Powershell as Administrator | ||
| 51 | ** Execute "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine | ||
| 52 | ** Execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux | ||
| 53 | ** Execute curl.exe -L -o ubuntu-2004.appx https://aka.ms/wslubuntu2004 | ||
| 54 | ** Execute Add-AppxPackage .\ubuntu-2004.appx | ||
| 55 | *** 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. | ||
| 56 | * Ubuntu should now be a runnable program (press windows key, type ubuntu) | ||
| 57 | * Open the ubuntu terminal, and finish the installation. | ||
| 58 | ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375 | ||
| 59 | |||
| 60 | ===3.4 Installation requirements Windows Server 2012 R2 === | ||
| 61 | |||
| 62 | |||
| 63 | === 3.5 Installation agent === | ||
| 64 | |||
| 65 | 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. | ||
| 66 | |||
| 67 | === 3.3 Cloud architecture for API Gateway === | ||
| 68 | |||
| 69 | [[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-install-runtime-images.png]] | ||
| 70 | |||
| 71 | == 4. Assignment == | ||
| 72 | |||
| 73 | Check out the cheatcheet for Docker command line: | ||
| 74 | |||
| 75 | [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] | ||
| 76 | |||
| 77 | == 5. Key takeaways == | ||
| 78 | |||
| 79 | * 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 | ||
| 80 | * eMagiz has a specific agent that manages the download of that image to the on-premises server | ||
| 81 | * 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. | ||
| 82 | |||
| 83 | |||
| 84 | |||
| 85 | == 6. Suggested Additional Readings == | ||
| 86 | |||
| 87 | N/A | ||
| 88 | |||
| 89 | == 7. Silent demonstration video == | ||
| 90 | |||
| 91 | N/A | ||
| 92 | |||
| 93 | )))((({{toc/}}))){{/container}}{{/container}} |