Changes for page Volume Mapping (On-premise)

Last modified by Erik Bakker on 2024/08/26 12:37

From 28.2 to 29.1 From 58.1 to 59.1

From version 29.1

edited by Erik Bakker
on 2022/06/10 13:22

Change comment: There is no comment for this version

To version 58.1

edited by Erik Bakker
on 2023/11/16 07:06

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Processing a File per Line
++Volume Mapping (On-premise)

Default language

...	...	@@ -1,0 +1,1 @@
	1	+en

Content

@@ -1,11 +1,13 @@
  {{container}}{{container layoutStyle="columns"}}(((
--In some cases, you want to treat each unique part of your input file as its message instead of processing the complete file as its message. In this microlearning, we will learn how you can process a (large) file on a per-line basis.
--Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
++{{warning}}
++Please note that this microlearning is for the new monitoring stack only.
++{{/warning}}
--* Last update: May 28th, 2021
--* Required reading time: 5 minutes
++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.
++Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
++
  == 1. Prerequisites ==
  * Basic knowledge of the eMagiz platform
@@ -12,93 +12,131 @@
  == 2. Key concepts ==
--This microlearning centers around learning how to process an incoming file per line.
++This microlearning centers around learning how to correctly set up your volume mapping so you can exchange file-based data on-premise.
--By processing per line, we mean: Splitting up the input into discernable pieces that each will become a unique message
++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 the other party writing or reading the data can access this path or when the data is only relevant within the context of eMagiz.
--* Easy way of reading a file line by line and sending it to eMagiz (Low on memory)
--* Ability to process each line based on distinctive logic that is relevant on line level
--* Can be used for flat file as well as XML input files
++There are several options for volume mapping for your on-premise machine.
++* Volume
++* Bind mount
++* Temporary file system
++* Named pipe
--== 3. Processing a File per Line ==
++== 3. Volume Mapping (On-premise) ==
--In some cases, you want to treat each unique part of your input file as its message instead of processing the complete file as its message. In this microlearning, we will learn how you can process a (large) file on a per-line basis.
++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.
--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 retrieve the file to a certain location. Within the context of this flow, we need to add functionality that will ensure that each line is read and processed separately and will become its unique message. To do so first enter "Start Editing" mode on flow level. After you have done so please add a file item reader message source to the flow. We will use this component to read and process our input file on a per-line basis.
++There are several options for volume mapping for your on-premise machine.
++* Machine volume
++* Bind mount
++* Network volume
++* Temporary file system
++* Named pipe
--The first step would be to define the directory from which we read our messages. As always reference to the directory with the help of a property.
++Below, we will explain the differences between the various options available for your volume mapping. But before we do, 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.
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--file-item-reader-directory.png]]
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-option-context-menu.png]]
--Secondly, just as when reading the file as a whole ensure that you use a filter to retrieve only the correct files from the directory.
++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.
--=== 3.1 Item reader Type ===
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-mapping-pop-up.png]]
--Now it is time to select our Item reader Type. As the help text of the eMagiz component suggest there are two choices with this component. The first (and most frequently used) option is the Flat file item reader. With this option, you can read each line within the flat file input file and output is at a separate message. The second option is called the Stax event item reader. With this option, you can read your input XML and output messages on a per-record basis.
++{{info}}Note that you should be in "Start editing" mode to make any changes to the configuration of your volume mapping.{{/info}}
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--item-reader-type-options.png]]
++=== 3.1 Volume ===
--Based on your choice the exact configuration will differ.
++The first Type available to you is volume. With this option, you create one or more folders on Docker relevant to that runtime to read and write **persistent** data. To configure this Type, you need to link the runtime volume to a machine volume (or network volume) you can create within the same pop-up. This means you can re-use a "Machine volume" or a "Network volume" over multiple runtimes (i.e., containers). We first need to define a machine (or network) volume to do so. Once we have done that, we can learn how to link the volume to the machine or network volume.
--==== 3.1.1 Stax Event Item Reader ====
++==== 3.1.1 Define Machine Volume ====
--For the Stax event item reader, you need to define the name of the element on which you want to split the XML and define whether you want to throw an error in case no such element exists in the input file (By (de)selecting the option Strict). The default setting of eMagiz is advisable for this option.
++So, we first open the tab called "Machine volume." Then, by pressing the "New" button, we can define a new "Machine volume." In the following pop-up, we can specify the name of a machine volume and tell whether the volume already exists on your docker installation.
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--stax-event-item-reader-config.png]]
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--machine-volumes-configuration.png]]
--==== 3.1.2 Flat File Item Reader ====
++Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
--For the Flat File item reader, there are some more choices and configurations to be made. There are three options you can choose from:
--- Pass through line mapper
--- Default line mapper
--- Pattern matching composite line mapper
++{{info}}When stating that the machine volume already exists, you can re-use the same machine volume across multiple runtimes (i.e., containers). This is especially useful when archiving data. You can create a central volume in which the data is stored, and through the linkage of the volume to the machine volume, you can subsequently structure your archiving folder. The paths will then look as follows, "/archive/runtimename"{{/info}}
--Each of these options has some advantages and disadvantages. Adhering to the best practices of eMagiz (i.e. no transformation in the entry) the best option would be to use the pass-through line mapper. As the name suggests this option does nothing except give a string back to the flow on a per line basis. However, choosing this option means that the actual transformation from that string to XML needs to happen later in the process (most likely in the onramp) with the help of a flat-file to XML transformer (more on that component in a later course).
++==== 3.1.2 Define Network Volume ====
--The other two options transform the input line into an XML output. So you win one step in the process. However, no standard eMagiz error handling is advisable when you start transforming data within the entry. So in case, something goes wrong to analyze the error will become more difficult. Furthermore, another potential disadvantage is that when one line fails the processing of the rest of the file also halts.
++So, we first open the tab called "Network volume." Then, by pressing the "New" button, we can define a new "Network volume." In the following pop-up, we can specify the name of a machine volume and configure the relevant information for a network volume. In most cases, a CIFS is used, and the only pertinent options that need to be filled in are the host, path, username, and password.
--For the remainder of this microlearning, we will assume that the option pass through line mapper is chosen.
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--network-volumes-configuration.png]]
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--flat-file-item-reader-passthrough.png]]
++Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
--As you can see on the Basic level we are done. However, it is always good to check out the settings on the Advanced tab, especially in this case, to see if there are additional configuration options that could benefit us. The setting of most interest, in this case, is the Lines to Skip setting (default setting is 0). With this setting, you can define whether or not you want to process the header line(s) that exists within your input file. The remainder of the settings is (in most cases) good the way eMagiz has set them up.
++{{info}}When configuring a network volume, the following information is relevant to know:
++* When you create a network volume to a folder that contains sub-folders, all sub-folders are shared automatically and can be accessed from the flow level
++* When dealing with multiple hosts, you must create a specific entry per host, as this follows the guiding security principles of the underlying infrastructure.{{/info}}
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--flat-file-item-reader-passthrough-advanced.png]]
++==== 3.1.3 Link Volume ====
--=== 3.2 Poller ===
++In the "Runtime volumes" tab, we push the "New" button to create a new "Runtime volume." In the following pop-up, we must select the Type we want to use. For this example, we use the Type called "Volume."
--Now that we have selected and configured the item reader type it becomes time to fill in the last part of the configuration, the poller. For polling eMagiz offers three options:
++{{info}} The relevant input fields will change based on your selection. {{/info}}
--- Fixed Delay Trigger
--- Fixed Rate Trigger
--- Cron Trigger
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]]
--Of these options, the cron trigger is used most frequently in eMagiz. The reason being is that you can define this option via a property that you can alter without having to alter the flow version in Create.
++The first thing we need to select is the "Volume." Once we have chosen our "Volume," we must set the Target specific for this runtime. This target defines the second part of the path to which the runtime will gain access. For example, when you fill in "/target", we can combine this with the "Volume" name to arrive at the correct directory from which eMagiz needs to read data (or write data to). So, in our case, in which we link the volume to the machine volume we created earlier, this would be "/file-directory/target."
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--poller-config.png]]
++The last setting we need to configure is to define the rights we will grant our runtime on the volume we create. The default setting is read/write rights for the runtime, which is usually sufficient. The result of following these steps will be the following.
--After finishing all these configuration steps we can press Save to save our work and ensure that we can process the input file on a per-line basis.
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume-filled-in.png]]
--== 4. Assignment ==
++{{warning}}Note the following when considering using the Volume option:
++* 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.
++* The Volume option and Machine volume combination can also be used for eMagiz-only information that needs to be persistable, such as archiving.
++* 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.
++{{/warning}}
--Configure an entry in which you define the component and configuration needed to process a file on a per-line basis.
--This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
++=== 3.2 Bind mount ===
--== 5. Key takeaways ==
++An alternative option to read and write **persistent** data is the "Bind mount" option. We generally advise using the "Volume" option because they perform better, and bind mounts depend on the host machine's directory structure and OS. However, only some external systems can adapt to this that easily. For example, the "Bind mount" option can interest your use case.
--* Easy way of reading a file line by line and sending it to eMagiz (Low on memory)
--* Ability to process each line based on distinctive logic that is relevant on line level
--* Can be used for flat file as well as XML input files
--* Try to avoid complex transformations within the entry
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount.png]]
--== 6. Suggested Additional Readings ==
++To configure a "Bind mount," you need to define a source and a target directory linked to each other. The source directory represents the directory on your local system (that might already be used currently to exchange files). The target directory defines a directory on your docker installation that the runtime can access.
--There are no suggested additional readings on this topic
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount-filled-in.png]]
--== 7. Silent demonstration video ==
++{{info}}Note that when you use this option, your directory reference in your flow should refer to the "target" directory configured here.{{/info}}
--This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
++=== 3.3 Temporary file system ===
--{{video attachment="novice-file-based-connectivity-processing-a-file-per-line.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
++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.
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]]
++
++To configure this option, you need a target location. On top of that, you can define the maximum size of the temporary file system.
++
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage-filled-in.png]]
++
++{{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}}
++
++=== 3.4 Named pipe ===
++
++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.
++
++=== 3.5 Deployment consequences ===
++
++{{warning}}
++* Note that the runtimes cannot be deployed correctly when the source directory **does not exist**. Consequently, no runtime on that machine will start up. One of the following two configurations displayed below are needed to find the source directory:
++** /mnt/host/{local-directory}
++** /run/desktop/mnt/host/{local-directory}
++* When the source directory can be found but the user has no access, the deployment will **fail** for the specific runtime in question with the volume mapping configured. All other runtimes (i.e., containers) will start up (pending other configuration issues).{{/warning}}
++
++== 4. Key takeaways ==
++
++* File-based communication on-premise changes in the new runtime architecture
++* There are two ways to store **persistent** data
++  ** Volume
++  ** Bind mount
++* 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
++* Before deploying, ensure that the various sources in your configuration exist and that access is granted to avoid problems while deploying.
++* The Temporary file storage option is the way to go when dealing with **non-persistent** data.
++
++== 5. Suggested Additional Readings ==
++
++If you are interested in this topic and want more information, please read the help text provided by eMagiz.
++
  )))((({{toc/}}))){{/container}}{{/container}}

Changes for page Volume Mapping (On-premise)

Summary

Details

Navigation