Skip to Content
Last modified by Erik Bakker on 2024/02/21 21:42
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
4 {{error}}
5 Note that the functionality mentioned in this microlearning will become obsolete when migrating to the 3rd generation runtime.
6 {{/error}}
7
8 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 Windows.
9
10 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
11
12 == 1. Prerequisites ==
13
14 * Basic knowledge of the eMagiz platform
15
16 == 2. Key concepts ==
17
18 This microlearning centers on editing the memory settings for an on-premise runtime that is running on Windows
19
20 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
21
22 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 Windows
23
24 * The key aspects are:
25 ** eMagiz can help you determine the correct size you need to configure via Design -> Architecture
26 ** You need access to the on-premise location to perform the action
27 ** Only change the wrapper.conf file. Nothing else
28
29 == 3. Edit memory for on-premise runtime (Windows) ==
30
31 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 Windows.
32
33 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 Windows
34
35 * The key aspects are:
36 ** eMagiz can help you determine the correct size you need to configure via Design -> Architecture
37 ** You need access to the on-premise location to perform the action
38 ** Only change the wrapper.conf file. Nothing else
39
40 === 3.1 Check adviced size ===
41
42 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.
43
44 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--context-menu-view.png]]
45
46 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.
47
48 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--pop-up-details.png]]
49
50 === 3.2 Edit memory ===
51
52 Now that we know what the advised size is we can navigate to our on-premise location to edit the memory settings. Below we will detail the various steps needed to make this happen.
53
54 1. At first we navigate to the etc folder of your runtime installation which is named according to the following naming convention -> emagiz*{technicalbusname}-{containertype}-{technicalnameofruntime}*{environment}. In this example that would mean emagiz_commupd-connector-ordsys_test.
55
56 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--etc-folder-location.png]]
57
58 2. Within this folder you will find a wrapper.conf file that is named based on the runtime name.
59
60 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--wrapper-conf-file.png]]
61
62 3. When you open this file you can change the memory settings, both heap, and metaspace. In the figures shown below, you can see which parts of the file you need to change to change the memory settings.
63
64 **Heap memory:**
65
66 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--heap-memory.png]]
67
68 **Metaspace memory:**
69
70 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--metaspace-memory.png]]
71
72 4. Save the file as administrator
73 5. Restart the runtime to ensure your changes have been actualized
74
75 == 4. Key takeaways ==
76
77 * The key aspects are:
78 ** eMagiz can help you determine the correct size you need to configure via Design -> Architecture
79 ** You need access to the on-premise location to perform the action
80 ** Only change the wrapper.conf file. Nothing else
81
82 == 5. Suggested Additional Readings ==
83
84 None
85 )))
86
87 ((({{toc/}}))){{/container}}
88 {{/container}}