Changes for page API Gateway Architecture
Last modified by Erik Bakker on 2024/09/02 16:04
From version 6.1
edited by Erik Bakker
on 2022/06/13 08:18
on 2022/06/13 08:18
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 - Edit memory for on-premiseruntime(Linux)1 +advanced-solution-architecture-apigw-architecture - Content
-
... ... @@ -1,6 +1,6 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 2 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.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. 4 4 5 5 Should you have any questions, please contact academy@emagiz.com. 6 6 ... ... @@ -11,24 +11,24 @@ 11 11 * Basic knowledge of the eMagiz platform 12 12 13 13 == 2. Key concepts == 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 Cloud14 +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 15 15 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 Linux16 +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 17 17 18 18 * The key aspects are: 19 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 action20 + ** You need access to the on-premise location to perform the action 21 21 ** Only change the wrapper.conf file. Nothing else 22 22 23 -== 3. Edit memory for on *premise runtime (Linux) ==23 +== 3. Edit memory for on-premise runtime (Linux) == 24 24 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.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. 26 26 27 -The focal point of this microlearning will be to learn how you can safely edit the memory settings for an on *premise runtime.27 +The focal point of this microlearning will be to learn how you can safely edit the memory settings for an on-premise runtime. 28 28 29 29 * The key aspects are: 30 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 action31 + ** You need access to the on-premise location to perform the action 32 32 ** Only change the wrapper.conf file. Nothing else 33 33 34 34 === 3.1 Check adviced size === ... ... @@ -43,7 +43,7 @@ 43 43 44 44 === 3.2 Edit memory on Linux based runtimes === 45 45 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.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. 47 47 48 48 * Log in via Putty by typing in the host and the port and press load 49 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 ... ... @@ -69,7 +69,7 @@ 69 69 70 70 * The key aspects are: 71 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 action72 + ** You need access to the on-premise location to perform the action 73 73 ** Only change the wrapper.conf file. Nothing else 74 74 75 75