Skip to Content
Last modified by Martijn Woudstra on 2022/08/25 12:16
Hide last authors
Martijn Woudstra 47.1 1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
4
5 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.
6
7 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
8
9 == 1. Prerequisites ==
10
11 * Basic knowledge of the eMagiz platform
12
13 == 2. Key concepts ==
14
15 This microlearning centers on editing the memory settings for an on-premise runtime that is running on Windows
16
17 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
18
19 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
20
21 * The key aspects are:
22 ** eMagiz can help you determine the correct size you need to configure via Design -> Architecture
23 ** You need access to the on-premise location to perform the action
24 ** Only change the wrapper.conf file. Nothing else
25
26 == 3. Edit memory for on-premise runtime (Windows) ==
27
28 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.
29
30 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
31
32 * The key aspects are:
33 ** eMagiz can help you determine the correct size you need to configure via Design -> Architecture
34 ** You need access to the on-premise location to perform the action
35 ** Only change the wrapper.conf file. Nothing else
36
37 === 3.1 Check adviced size ===
38
39 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.
40
41 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--context-menu-view.png]]
42
43 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.
44
45 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--pop-up-details.png]]
46
47 === 3.2 Edit memory ===
48
49 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.
50
51 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.
52
53 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--etc-folder-location.png]]
54
55 2. Within this folder you will find a wrapper.conf file that is named based on the runtime name.
56
57 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--wrapper-conf-file.png]]
58
59 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.
60
61 **Heap memory:**
62
63 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--heap-memory.png]]
64
65 **Metaspace memory:**
66
67 [[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-edit-memory-on-premise-runtime-windows--metaspace-memory.png]]
68
69 4. Save the file as administrator
70 5. Restart the runtime to ensure your changes have been actualized
71
72 == 4. Assignment ==
73
74 As this is a more theoretical microlearning we do not have an assignment
75
76 == 5. Key takeaways ==
77
78 * The key aspects are:
79 ** eMagiz can help you determine the correct size you need to configure via Design -> Architecture
80 ** You need access to the on-premise location to perform the action
81 ** Only change the wrapper.conf file. Nothing else
82
83 == 6. Suggested Additional Readings ==
84
85 None
86
87 == 7. Silent demonstration video ==
88
89 As this is a more theoretical microlearning we have no video for this
90 )))
91
92 ((({{toc/}}))){{/container}}
93 {{/container}}
94