Changes for page Volume Mapping (On-premise)

Summary

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

Details

Page properties

Content

...	...	@@ -89,9 +89,8 @@
89	89	* In the case of using the Volume option in combination with a Machine volume, the external system with which you exchange data on-premise via a file-based method needs to be able to write or read the data from the volume (i.e., directory) you have configured. Should this be a problem, the Bind mount alternative discussed below should be considered.
90	90	* The Volume option and Machine volume combination can also be used for eMagiz-only information that needs to be persistable, such as archiving.
91	91	* In the case of using the Volume option in combination with a Network volume, the path to read and write from becomes what you define in the target field.
92		-* In case of mapping a volume on a windows host machine to another one on a windows docker runtime when writing the source/target paths, the following small adjustment is required:
93		-** In the source/target path:
94		-a. All “\” in the path should be written as “/”. Example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp
	92	+* In case of mapping a volume on a windows host machine to another one on a windows docker runtime, the following small adjustment is required when writing the source/target paths:
	93	+** All “\” in the source/target path should be written as “/”. For example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp.
95	95
96	96	{{/warning}}
97	97
...	...	@@ -107,6 +107,11 @@
107	107
108	108	{{info}}Note that when you use this option, your directory reference in your flow should refer to the "target" directory configured here.{{/info}}
109	109
	109	+{{warning}}
	110	+When configuring a bind mount on a windows host machine to another one on a windows docker runtime, the following small adjustment is required when writing the source/target paths:
	111	+**All “\” in the source/target path should be written as “/”. For example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp.
	112	+{{/warning}}
	113	+
110	110	=== 3.3 Temporary file system ===
111	111
112	112	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.
...	...	@@ -117,12 +117,17 @@
117	117
118	118	[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage-filled-in.png]]
119	119
120		-{{warning}}We strongly advise you to define this number so that you can limit the potential impact this solution can have on the stability of your machine.{{/warning}}
	124	+{{warning}}
	125	+We strongly advise you to define this number so that you can limit the potential impact this solution can have on the stability of your machine. {{/warning}}
121	121
122	122	=== 3.4 Named pipe ===
123	123
124		-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.
	129	+*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.
125	125
	131	+{{warning}}
	132	+* When configuring a pipe path on a windows host machine to another one on a windows docker runtime, the following small adjustment is required when writing the source/target paths:
	133	+** All “\” in the source/target path should be written as “/”. For example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp.{{/warning}}
	134	+
126	126	=== 3.5 Deployment consequences ===
127	127
128	128	{{warning}}