Changes for page Volume Mapping (On-premise)
Last modified by Erik Bakker on 2024/08/26 12:37
From version 46.1
edited by Erik Bakker
on 2022/10/31 11:27
on 2022/10/31 11:27
Change comment:
There is no comment for this version
To version 48.1
edited by Erik Bakker
on 2022/10/31 15:18
on 2022/10/31 15:18
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -76,6 +76,16 @@ 76 76 77 77 === 3.3 Temporary file system === 78 78 79 +If you do not want to work with **persistent** data but have a need for **non-persistent** data the temporary file system option is for you. This way you can increase the container’s performance by avoiding writing into the container’s writable layer. 80 + 81 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]] 82 + 83 +To configure this option you need a target location. On top of that you can define the maximum size of the temporary file system. 84 + 85 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage-filled-in.png]] 86 + 87 +{{warning}}We strongly advice to define this number as that way you can limit the potential impact this solution can have on the stability of your machine.{{/warning}} 88 + 79 79 === 3.4 Named pipe === 80 80 81 81 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. ... ... @@ -82,27 +82,26 @@ 82 82 83 83 == 4. Assignment == 84 84 85 - Configureanentryinwhich youbuild the archivingand thecleanup ofthe archiving.95 +Navigate to Deploy -> Architecture and take a look at the Volume mapping options, read the help texts and play around with the settings a bit (if it is not a customer environment). 86 86 This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment. 87 87 88 88 == 5. Key takeaways == 89 89 90 -* Archiving is used for audit purposes 91 -* Archiving is used for retry scenarios 92 -* Ensure that data is cleaned after a retention period to keep in control of the data 93 -* Don't forget the max messages per poll 100 +* File based communication on-premise changes in the new runtime architecture 101 +* There are two ways to store **persistent** data 102 + ** Volume 103 + ** Bind mount 104 +* The Volume option is considered the best alternative because they have better performance and bind mounts are dependent on the directory structure and OS of the host machine 105 +* When you want to deal with **non-persistent** data the Temporary file storage option is the way to go. 94 94 95 95 == 6. Suggested Additional Readings == 96 96 97 -If you are interested in this topic and want more information on it please read the help text provided by eMagiz and check out the following store content:109 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz. 98 98 99 -* [[File Archiving>>doc:Main.eMagiz Store.Accelerators.File Archiving.WebHome||target="blank"]] 100 -* [[Delete Folder(s)>>doc:Main.eMagiz Store.Accelerators.Delete Folder(s).WebHome||target="blank"]] 101 - 102 102 == 7. Silent demonstration video == 103 103 104 104 This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned. 105 105 106 - {{video attachment="novice-file-based-connectivity-characterset.mp4" reference="Main.Videos.Microlearning.WebHome"/}}115 +TBA 107 107 108 108 )))((({{toc/}}))){{/container}}{{/container}}