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.
Should you have any questions, please contact academy@emagiz.com.
- Last update: June 24th 2021
- Required reading time: 10 minutes
1. Prerequisites
- Advanced knowledge of the eMagiz platform
- Good understanding of eMagiz runtimes in general
2. Key concepts
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
3. On-premises deployments
3.1 Installation requirements
Below the list of requirements for an on-premises deployment
- Windows Server or Linux Server
- Installed Docker software
- Server connected to the internet whereby the firewall doesn't prevent data traffic going outwards to the Internet
- In case there are outgoing firewall rules, eMagiz can provide the specific URL's and port numbers in order to update the firewall
- Sufficient resources inline with the requirements of the eMagiz runtimes. See this microlearning
3.2 Installation agent
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.
3.3 Cloud architecture for API Gateway
4. Assignment
There is no specific assignment for this microlearning.
5. Key takeaways
- eMagiz will help to determine the needed memory via the Design Architecture page.
- 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
- When you exceed such a threshold you should upgrade (or downgrade) your memory in consultation with your partner manager
- Overhead for OS and support functionality (auto-healing, alerting, monitoring) needs to be taken into account
- Calculating memory can be challenging. Always confer with others before taking action
- You can compare your calculations with the calculations of eMagiz
- The calculations and logic described below are applicable for the Messaging, API Gateway and Event Streaming pattern
6. Suggested Additional Readings
If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
7. Silent demonstration video
N/A