Skip to Content
Last modified by Bas Elzinga on 2024/12/17 12:20
From version 4.1
edited by eMagiz
on 2022/06/24 15:00
Change comment: There is no comment for this version
To version 5.1
edited by eMagiz
on 2022/06/24 15:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -27,7 +27,7 @@
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.
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. 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  
... ... @@ -39,13 +39,9 @@
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
42 +* 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
43 +* eMagiz has a specific agent that manages the download of that image to the on-premises server
44 +* 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