Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 48.1
edited by Erik Bakker
on 2022/10/31 15:18
Change comment: There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2022/10/31 11:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -76,16 +76,6 @@
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 -
89 89  === 3.4 Named pipe ===
90 90  
91 91  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.
... ... @@ -92,26 +92,27 @@
92 92  
93 93  == 4. Assignment ==
94 94  
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).
85 +Configure an entry in which you build the archiving and the clean up of the archiving.
96 96  This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
97 97  
98 98  == 5. Key takeaways ==
99 99  
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.
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
106 106  
107 107  == 6. Suggested Additional Readings ==
108 108  
109 -If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
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:
110 110  
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 +
111 111  == 7. Silent demonstration video ==
112 112  
113 113  This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
114 114  
115 -TBA
106 +{{video attachment="novice-file-based-connectivity-characterset.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
116 116  
117 117  )))((({{toc/}}))){{/container}}{{/container}}