Changes for page Key differences Design & Deploy Architecture
Last modified by Erik Bakker on 2024/09/02 16:06
From version 12.1
edited by Erik Bakker
on 2022/10/03 11:32
on 2022/10/03 11:32
Change comment:
There is no comment for this version
To version 7.2
edited by Erik Bakker
on 2022/06/13 08:20
on 2022/06/13 08:20
Change comment:
Update document after refactoring.
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - KeydifferencesDesign& Deploy Architecture1 +advanced-solution-architecture-apigw-architecture - Content
-
... ... @@ -1,61 +1,85 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -This micro-learning will focus on some differences between the Design and Deploy architecture 3 3 4 -S houldyou haveany questions,pleasecontact[[academy@emagiz.com>>mailto:academy@emagiz.com]].3 +Sometimes you have runtimes running on-premises. What we mean by that is that the runtimes are running within a data center of the customer instead of running in the eMagiz Cloud. For running a runtime on-premise we support running them on either Windows or Linux as the operating system. In this microlearning, we will learn how you can edit the memory settings of a runtime that is deployed on-premise on Linux. 5 5 5 +Should you have any questions, please contact academy@emagiz.com. 6 + 7 +* Last update: April 5th, 2022 8 +* Required reading time: 5 minutes 9 + 6 6 == 1. Prerequisites == 7 -* Intermediate knowledge of the eMagiz platform 8 -* Good working experience in the Design & Deploy architecture aspects 11 +* Basic knowledge of the eMagiz platform 9 9 10 10 == 2. Key concepts == 11 -Th e DesignArchitecture is the placewhere thearchitecture ofthentegrationmodelis forged.It allowsto placeSystemstoCloudor On-premisesconnector machinessothathybridcloudarchitecturesarepossible.TheDeployArchitectureisthe placewherethe Design architectureis effectuated.Incase a system isdedtoa Cloud Connector machineforinstance,theDeployarchitecturewill allows to actuallydeploy that runtime.14 +This microlearning centers on editing the memory settings for an on-premise runtime that is running on Linux. With an on-premise runtime we mean: A runtime that is running within a data center of the customer instead of running in the eMagiz Cloud 12 12 13 - == 3. KeydifferencesinviewsDeploy&Design==16 +The focal point of this microlearning will be to learn how you can safely edit the memory settings for an on-premise runtime running on Linux 14 14 15 -The System is the key notion for a eMagiz runtime to get created. The eMagiz runtime is a Java based application container in which flows can be made active or operational. In most cases, all Systems in Design are to be located on a machine to effectuate these runtimes on the machines. 18 +* The key aspects are: 19 + ** eMagiz can help you determine the correct size you need to configure via Design *> Architecture 20 + ** You need access to the on-premise location to perform the action 21 + ** Only change the wrapper.conf file. Nothing else 16 16 17 - However,insome cases the Deploy architecture looksdifferentcompared tothe Design architecture. In a sense that some systemdon't get "created"inDeploy. Theseare the reasons for Systems not to appearinDeploy architecture:23 +== 3. Edit memory for on-premise runtime (Linux) == 18 18 19 -* System is only used for API Gateway Access 20 -The system acts as a role and user, and no other integrations are used to and from that system. You can recognize the blue lines with blue rounded boxes containing the number of operations. These systems will be displayed in Design yet not in Deploy architecture. No runtime application is needed as no flows are supposed to run inside these systems. Multi-tenant systems that act as role (with tenants being the users) are also not displayed as system in Deploy Architecture. Below an example of such a case: 25 +Sometimes you have runtimes running on-premises. What we mean by that is that the runtimes are running within a data center of the customer instead of running in the eMagiz Cloud. For running a runtime on-premise we support running them on either Windows or Linux as the operating system. In this microlearning, we will learn how you can edit the memory settings of a runtime that is deployed on-premise. 21 21 22 - [[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-1.png]]27 +The focal point of this microlearning will be to learn how you can safely edit the memory settings for an on-premise runtime. 23 23 24 -* System that is used only for Event Streaming integrations 25 -The same applies to systems that are displayed for registering Producers and Consumers for Event Streaming. These systems are not displayed in Deploy Architecture. 29 +* The key aspects are: 30 + ** eMagiz can help you determine the correct size you need to configure via Design *> Architecture 31 + ** You need access to the on-premise location to perform the action 32 + ** Only change the wrapper.conf file. Nothing else 26 26 27 - [[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-2.png]]34 +=== 3.1 Check adviced size === 28 28 29 -* Systems accessed via Exit Gates only 30 -Applications that accessed via API Gateway operations only are also no displayed in the Deploy Architecture. Exit gates are accessing these applications (displayed as systems) yet the exit gate will run on the gateway container runtime. Therefore, these system don't require any flow to deploy on so no runtimes gets created. 36 +Within Design Architecture you can see for each connector runtime what the advised sizing of eMagiz is based on how you have configured your integration data model. To do so navigate to Design *> Architecture and open the context menu on connector runtime level via a right mouse click. 31 31 32 -[[image:Main.Images.Microlearning.WebHome@ advanced-solution-architecture-diffs-design-deploy-3.png]]38 +[[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--context-menu-view.png]] 33 33 34 - There is an exceptionforthat. In case the exit gate is required torunon the on-premisesinfrastructureofthe client for securityreasons,the runtimedoes get created andwill bedisplayed thereforein theDeploy architecture. Applytoenvironmentwillnot result in thephysical deploymentoftheruntime, but'sdisplayedso that theDeploymentplancanindicaterogresson deployment.TheoptionSplitGateway needstobecheckedinhe Design phase40 +When selecting the option View container a pop*up will be shown. Within this pop*up, you will see the advised heap and non*heap memory settings of that particular runtime. 35 35 36 -[[image:Main.Images.Microlearning.WebHome@ advanced-solution-architecture-diffs-design-deploy-4.png]]42 +[[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--pop-up-details.png]] 37 37 38 -* Hybrid systems 39 -In case a system will contain not only a user management like integration but also another integration (i.e. Messaging) the runtime will be displayed in Deploy architecture as usual. A flow or series of flows need to be deployed on the runtime 44 +=== 3.2 Edit memory on Linux based runtimes === 40 40 41 -* Best practice for Design Architecture 42 -In Design Architecture it is adviced to create one or more on-premises machine that is toggled excluded. Each of these machine will act as a location where runtime not used in Deploy are put. So alignment between Design and Deploy is improved. 46 +Now that we know what the advised size is we can navigate to our on-premise installation location to edit the memory settings. Below we will detail the various steps needed to make this happen. 43 43 44 -[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-4.png]] 48 +* Log in via Putty by typing in the host and the port and press load 49 +* When asked for credentials fill in credentials (Be aware, Linux does not acceapt ctrl+v and does not show the password or an indication of the password). Right mouse click to copy the password and press enter 50 +* Navigate to the directory where you have installed the runtime (Command is: cd {directory structure}) 51 +* Open the folder related to the runtime you want to change (Command is: cd emagiz_{technicalbusname}-{containertype}-{techincalnameruntime}_{environment}). 52 +* Open the etc folder within your runtime installation (Command is: cd etc) 53 +* Type in the following command: sudo vi emagiz and press Tab. This way Linux should auto suggest the so called wrapper.conf to be edited and press Enter if so 54 +* Type "i" to enter insert mode 55 +* Change the values of heap and or metaspace memory you want to change (you can navigate through the document with your arrow keys) 56 +* Press ESC and then type ":wq!" then press Enter to save the changes and exit Edit mode. Note: If you would like to exit the file without making any changes press ESC, then type ":q!" and press Enter 57 +* Restart the runtime by executing the correct restart command: 58 + ** systemd type: sudo systemctl restart <SERVICE_NAME> 59 + ** SystemV Type: sudo /etc/init.d/<SERVICE_NAME>-service restart 45 45 61 + 62 + 63 + 46 46 == 4. Assignment == 47 47 48 - Pleaseexperimentwiththe options ineMagizDesign& Deploy Architecture tounderstand theabovepoints.66 +As this is a more theoretical microlearning we do not have an assignment 49 49 50 50 == 5. Key takeaways == 51 -Design and Deploy architecture can differ in view * specific reasons exit which are described in this microlearning. 52 52 70 +* The key aspects are: 71 + ** eMagiz can help you determine the correct size you need to configure via Design *> Architecture 72 + ** You need access to the on-premise location to perform the action 73 + ** Only change the wrapper.conf file. Nothing else 74 + 75 + 76 + 53 53 == 6. Suggested Additional Readings == 54 54 55 - There are nosuggested additional readings on this topic79 +None 56 56 57 57 == 7. Silent demonstration video == 58 58 59 - Thereisnodemonstration videoof thisfunctionality.83 +As this is a more theoretical microlearning we have no video for this 60 60 61 61 )))((({{toc/}}))){{/container}}{{/container}}