Changes for page Edit on-premise runtime memory settings (Linux)

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,31 +1,34 @@
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		-Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
	5	+Should you have any questions, please contact academy@emagiz.com.
6	6
	7	+* Last update: April 5th, 2022
	8	+* Required reading time: 5 minutes
	9	+
7	7	== 1. Prerequisites ==
8	8	* Basic knowledge of the eMagiz platform
9	9
10	10	== 2. Key concepts ==
11		-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
12	12
13		-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
14	14
15	15	* The key aspects are:
16	16	** eMagiz can help you determine the correct size you need to configure via Design *> Architecture
17		- ** 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
18	18	** Only change the wrapper.conf file. Nothing else
19	19
20		-== 3. Edit memory for on-premise runtime (Linux) ==
	23	+== 3. Edit memory for on*premise runtime (Linux) ==
21	21
22		-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.
23	23
24		-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.
25	25
26	26	* The key aspects are:
27	27	** eMagiz can help you determine the correct size you need to configure via Design *> Architecture
28		- ** 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
29	29	** Only change the wrapper.conf file. Nothing else
30	30
31	31	=== 3.1 Check adviced size ===
...	...	@@ -40,7 +40,7 @@
40	40
41	41	=== 3.2 Edit memory on Linux based runtimes ===
42	42
43		-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.
44	44
45	45	* Log in via Putty by typing in the host and the port and press load
46	46	* 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
...	...	@@ -55,6 +55,9 @@
55	55	** systemd type: sudo systemctl restart <SERVICE_NAME>
56	56	** SystemV Type: sudo /etc/init.d/<SERVICE_NAME>-service restart
57	57
	61	+
	62	+
	63	+
58	58	== 4. Assignment ==
59	59
60	60	As this is a more theoretical microlearning we do not have an assignment
...	...	@@ -63,9 +63,11 @@
63	63
64	64	* The key aspects are:
65	65	** eMagiz can help you determine the correct size you need to configure via Design *> Architecture
66		- ** 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
67	67	** Only change the wrapper.conf file. Nothing else
68	68
	75	+
	76	+
69	69	== 6. Suggested Additional Readings ==
70	70
71	71	None