Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 69.1
edited by Erik Bakker
on 2024/03/05 08:56
Change comment: There is no comment for this version
To version 65.1
edited by Erik Bakker
on 2023/11/26 20:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,9 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 +
3 +{{warning}}
4 +Please note that this microlearning is for the new monitoring stack only.
5 +{{/warning}}
6 +
2 2  When you need to read and write files from an on-premise disk, you need to know the path in which the data is stored and ensure that the docker container in your runtime(s) running has access to this path. There are several ways of dealing with this challenge. This microlearning will discuss the various alternatives and best approaches in these scenarios.
3 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
... ... @@ -11,7 +11,7 @@
11 11  
12 12  This microlearning centers around learning how to correctly set up your volume mapping so you can exchange file-based data on-premise.
13 13  
14 -By volume mapping, we mean creating a configuration through which the docker container can read and write data on a specific path on an on-premise machine. Note that the data can also be stored inside the docker container when (1) the other party writing or reading the data can access this path or (2) when the data is only relevant within the context of eMagiz.
19 +By volume mapping, we mean Creating a configuration through which the docker container can read and write data on a specific path on an on-premise machine. Note that the data can also be stored inside the docker container when (1) the other party writing or reading the data can access this path or (2) when the data is only relevant within the context of eMagiz.
15 15  
16 16  There are several options for volume mapping for your on-premise machine.
17 17  * Volume
... ... @@ -30,11 +30,11 @@
30 30  * Temporary file system
31 31  * Named pipe
32 32  
33 -Below, we will explain the differences between the various options available for your volume mapping. But before we do this, we explain how to set up this configuration within eMagiz. First, you must navigate to Deploy -> Architecture on the model level. This overview lets you access the Volume mapping per runtime deployed on-premise. And then, you can right-click on the runtime to access the context menu.
38 +Below, we will explain the differences between the various options available for your volume mapping. But before we do this, we explain how to set up this configuration within eMagiz. Then, you must navigate to Deploy -> Architecture on the model level. This overview lets you access the Volume mapping per runtime deployed on-premise. To do so, you can right-click on the runtime to access the context menu.
34 34  
35 35  [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-option-context-menu.png]]
36 36  
37 -Right after you click this option, you will see the following pop-up. In this pop-up, you can define the machine-level, runtime-level, and network-level volumes (more on this volume levels later). This pop-up page is the starting point for configuring your volume mapping. We will walk through each available option and explain how they work and should be configured.
42 +When you click this option, you will see the following pop-up. In this pop-up, you can define the machine-level, runtime-level, and network-level volumes. More on that later. This is the starting point for configuring your volume mapping. We will walk through each available option and explain how they work and should be configured.
38 38  
39 39  [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-mapping-pop-up.png]]
40 40  
... ... @@ -108,8 +108,6 @@
108 108  
109 109  === 3.3 Temporary file system ===
110 110  
111 -{{info}}This option is only relevant when running on **Linux**.{{/info}}
112 -
113 113  The temporary file system option is for you if you do not want to work with **persistent** data but require **non-persistent** data. This way, you can increase the container's performance by avoiding writing into the container's writable layer.
114 114  
115 115  [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]]
... ... @@ -123,10 +123,6 @@
123 123  
124 124  === 3.4 Named pipe ===
125 125  
126 -{{info}}This option is only relevant when running on **Windows**.{{/info}}
127 -
128 -A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients. All instances of a named pipe share the same pipe name, but each instance has its own buffers and handles, and provides a separate conduit for client/server communication. Any process can access named pipes, subject to security checks, making named pipes an easy form of communication between related or unrelated processes.
129 -
130 130  *The named pipe option can be selected, but we yet have to see a valid use case within the context of eMagiz for using this option. Therefore, we won't discuss this option further in this microlearning.
131 131  
132 132  {{warning}}