Changes for page Volume Mapping (On-premise)
Last modified by Erik Bakker on 2024/08/26 12:37
From version 49.1
edited by Erik Bakker
on 2022/10/31 15:23
on 2022/10/31 15:23
Change comment:
There is no comment for this version
To version 41.1
edited by Erik Bakker
on 2022/10/31 09:07
on 2022/10/31 09:07
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -42,76 +42,67 @@ 42 42 43 43 === 3.1 Volume === 44 44 45 -T hefirstType available toyouisVolume.With thisoption,youcreateoneormore folders onDockerrelevantto thatruntimetoread and write**persistent**data. Toconfigure thisType,youneedto linkthe runtime volume to amachinevolumeyoucancreatewithinthesamepop-up.Thismeansyou canre-usea"Machinevolume"overultipleruntimes(i.e.,containers).45 +To make this work in eMagiz you need to navigate to the Create phase of eMagiz and open the entry flow in which you want to archive the files. Within the context of this flow, we need to add functionality that will ensure that each input file is archived and cleaned up when older than three days. To do so first enter "Start Editing" mode on flow level. The first decision we have to take is how we are going to name the files within the archiving. The best practice, in this case, is the original filename + the current time as a suffix. You can define this by dragging a format file name generator (support object) to the canvas. 46 46 47 - So, we first open the tab called "Machine volume." Then, by pressingthe"New"button, wecandefine a new "Machinevolume." In the pop-up that follows, weanspecifythe name of a machinevolume and tell whether the Volumealready exists onyour dockerinstallation ornot.47 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--file-name-generator.png]] 48 48 49 - [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--machine-volumes-configuration.png]]49 +After we have done this please add a file outbound channel adapter to the flow including an input channel. Ensure that you use a property for the directory that references another directory compared to the input directory to prevent creating an infinite loop. 50 50 51 - Once you havedone so, we press "Save" and switch back to the "Runtime volumes" tab. Then, we push the "New" button tocreate anew "Runtimevolume." Inthe following pop-up, werst needtoselecthe Type we want to use. Forthis example, we use the Typecalled "Volume." Basedon your selection, the relevant input fieldswillchange.51 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--archiving-config-file-outbound-basic.png]] 52 52 53 - [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]]53 +Now that we have configured the basics let us turn our attention to the advanced configuration. In the advanced tab of this component, we need to select the file name generator to ensure that the files are named correctly. In case you process each line separately you have to choose whether to save them as separate files in the archive or by appending them again. This can be achieved by selecting the correct Mode. In most cases, however, the default Mode of Replace will suffice. 54 54 55 - The first thing we need to select is the "Machine volume." Once we havechosen our "Machine volume," we must set the Targetspecific for this runtime.This target defines the second partof thepath to which theruntime will gainaccess.Forexample, whenyoufill in "/target", wecan combinehis with the "Machinevolume"name to arrive at the correct directoryfrom which eMagiz needs toread data (or write data to). So in our case,this wouldbe "/file-directory/target."55 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--archiving-config-file-outbound-advanced.png]] 56 56 57 -The last settingweneedtoconfigure is to definewhichrightswewillgrant our runtimeon theVolume we arecreating.Thedefaultsettingis read/write rightsforthe runtime,which issufficient inmostcases. The result offollowingthesestepswillbe the following.57 +The moment you are satisfied press Save. Now that we have configured this it becomes time to determine how we get the needed input to write to our archive. In the example we are using here we want to archive our input file so we need to ensure that the data we received is written to the archive as soon as possible. To do so place a wiretap on the first channel after retrieving the file. This will make sure that the message is archived before processed further. The result should be something as shown below. Note that this same piece of logic could be applied in other flows within the eMagiz platform in a similar manner. 58 58 59 -[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity- volume-mapping-on-premise--runtime-volumes-configuration-type-volume-filled-in.png]]59 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--archiving-result.png]] 60 60 61 - {{warning}}Notethatwhen you use the Volumeoption, the external system with which you exchangedata on-premisevia a file-based method needsto be able to write or read the data from the Volume (i.e., directory) youhave configured in Docker. Should this be a problem, the Bind mount alternativediscussed below should be considered.{{/warning}}61 +=== 3.2 Clean up the Archive === 62 62 63 - ===3.2Bind mount===63 +To ensure that the data is not kept indefinitely we need to clean up the archive. We do so to prevent problems with disk space but also to prevent data leaks of old data that could impact the privacy of others. Before we can set up the logic in eMagiz we need to talk to the customer to see what an acceptable term is within which the data is kept. In most cases, this is a week or two weeks. In this example, we have chosen three days. 64 64 65 - Analternativeoptiontoreadandwrite**persistent**dataisto use the"Bind mount" option.In general,weadviseusingthe"Volume"optionbecausetheyhavebetterperformance,andbindmountsdependonthehostmachine'sdirectorystructureandOS.However,onlysome externalsystemscan adapttothisthateasily. Forxample, the"Bindmount"optioncaninterestyourusecase.65 +Now that we know the limit it is time to configure the components. We start with a composite file filter (support object). Within this filter, we at least define how old a file must be before it can be deleted (in milliseconds). If we turn three days into milliseconds we get 259200000. Furthermore, we at least define that we only want to delete regular files. 66 66 67 -[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity- volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount.png]]67 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--file-list-filter-for-archive-cleanup.png]] 68 68 69 - To configurea"Bindmount,"youneedtodefinea source andargetdirectorylinkedto eachother.Thesourcedirectory representsthe directoryon your local system(thatmight alreadybe usedcurrentlytoexchangefiles).Thetargetdirectorydefinesadirectoryonyourdockerinstallation thattheruntimecan access.69 +Having done so we can add a file inbound channel adapter to the canvas including an output channel. Ensure that the property reference for the directory matches the one you have used before in the outbound channel adapter. Furthermore link the filter to the component and define the poller according to the best practice. 70 70 71 - {{warning}}Notethat whenthesourcedirectory doesnotexist, theruntimes cannotbe deployedcorrectly.{{/warning}}71 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--file-inbound-archive-cleanup.png]] 72 72 73 - [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount-filled-in.png]]73 +One thing we should not forget within this configuration is to set the Max messages per poll on the Advanced tab of the poller-configuration to a sufficiently high number (i.e. 50). If you forget to do so and you only check once a day it will mean that only one message will be deleted that day. 74 74 75 - {{info}}Note that whenyou usethisption, your directory referencenyourw shouldrefer to the "target" directory configured here.{{/info}}75 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--file-inbound-archive-cleanup-max-messages-per-poll.png]] 76 76 77 - ===3.3Temporary file system===77 +Now eMagiz will check on a set time interval whether there are files that are older than three days that are ready for deletion. One last step to go. This last step will ensure that all files that fit the bill will be deleted from the archive. Simply add a standard service activator to the canvas and define the following SPeL expression within the component: payload.delete(). 78 78 79 - The temporary filesystem optionis for you if you do not want to work with **persistent** data butrequire **non-persistent** data.This way, you canncreasethecontainer's performance by avoiding writinginto theontainer's writablelayer.79 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--archive-cleanup-deletion.png]] 80 80 81 - [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]]81 +This will ensure that each file that is retrieved will indeed be deleted from the archive. 82 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 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}} 88 - 89 -=== 3.4 Named pipe === 90 - 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 - 93 93 == 4. Assignment == 94 94 95 - NavigatetoDeploy->Architectureandlook attheVolume mappingoptions, read thehelp texts,andplayaroundwiththesettings (if it is notacustomerenvironment).96 -This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment. 85 +Configure an entry in which you build the archiving and the clean up of the archiving. 86 +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 ,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 -This video demonstrates how you could have handled the assignment and gives context to what you have just learned.104 +This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned. 114 114 115 - TBA106 +{{video attachment="novice-file-based-connectivity-characterset.mp4" reference="Main.Videos.Microlearning.WebHome"/}} 116 116 117 117 )))((({{toc/}}))){{/container}}{{/container}}