Changes for page Edit on-premise runtime memory settings (Linux)
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
on 2023/01/24 15:36
Change comment:
There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2022/06/13 08:20
on 2022/06/13 08:20
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,13 +1,12 @@ 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}} 6 - 7 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. 8 8 9 -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. 10 10 7 +* Last update: April 5th, 2022 8 +* Required reading time: 5 minutes 9 + 11 11 == 1. Prerequisites == 12 12 * Basic knowledge of the eMagiz platform 13 13 ... ... @@ -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 ... ... @@ -70,6 +70,8 @@ 70 70 ** 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