Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:20
From version 10.1
edited by Erik Bakker
on 2023/01/24 15:36
Change comment: There is no comment for this version
To version 6.1
edited by Erik Bakker
on 2022/06/13 08:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,35 +1,34 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
3 -{{error}}
4 -Note that the functionality mentioned in this microlearning will become obsolete when migrating to the 3rd generation runtime.
5 -{{/error}}
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.
6 6  
7 -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 +Should you have any questions, please contact academy@emagiz.com.
8 8  
9 -Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 +* Last update: April 5th, 2022
8 +* Required reading time: 5 minutes
10 10  
11 11  == 1. Prerequisites ==
12 12  * Basic knowledge of the eMagiz platform
13 13  
14 14  == 2. Key concepts ==
15 -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
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
16 16  
17 -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
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
18 18  
19 19  * The key aspects are:
20 20   ** eMagiz can help you determine the correct size you need to configure via Design *> Architecture
21 - ** You need access to the on-premise location to perform the action
20 + ** You need access to the on*premise location to perform the action
22 22   ** Only change the wrapper.conf file. Nothing else
23 23  
24 -== 3. Edit memory for on-premise runtime (Linux) ==
23 +== 3. Edit memory for on*premise runtime (Linux) ==
25 25  
26 -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.
27 27  
28 -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.
29 29  
30 30  * The key aspects are:
31 31   ** eMagiz can help you determine the correct size you need to configure via Design *> Architecture
32 - ** You need access to the on-premise location to perform the action
31 + ** You need access to the on*premise location to perform the action
33 33   ** Only change the wrapper.conf file. Nothing else
34 34  
35 35  === 3.1 Check adviced size ===
... ... @@ -44,7 +44,7 @@
44 44  
45 45  === 3.2 Edit memory on Linux based runtimes ===
46 46  
47 -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.
48 48  
49 49  * Log in via Putty by typing in the host and the port and press load
50 50  * 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
... ... @@ -59,6 +59,9 @@
59 59   ** systemd type: sudo systemctl restart <SERVICE_NAME>
60 60   ** SystemV Type: sudo /etc/init.d/<SERVICE_NAME>-service restart
61 61  
61 +
62 +
63 +
62 62  == 4. Assignment ==
63 63  
64 64  As this is a more theoretical microlearning we do not have an assignment
... ... @@ -67,9 +67,11 @@
67 67  
68 68  * The key aspects are:
69 69   ** eMagiz can help you determine the correct size you need to configure via Design *> Architecture
70 - ** You need access to the on-premise location to perform the action
72 + ** You need access to the on*premise location to perform the action
71 71   ** Only change the wrapper.conf file. Nothing else
72 72  
75 +
76 +
73 73  == 6. Suggested Additional Readings ==
74 74  
75 75  None