Changes for page Volume Mapping (On-premise)

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

From 30.1 to 30.2 From 43.1 to 44.1

From version 30.2

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

Change comment: Update document after refactoring.

To version 43.1

edited by Erik Bakker
on 2022/10/31 10:25

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 @@
--novice-file-based-connectivity-characterset
++Volume Mapping (On-premise)

Default language

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

Content

@@ -1,11 +1,9 @@
  {{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.
++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 make sure that the docker container in your runtime(s) running has access to this path. There are several ways of dealing with this challenge. First, 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]].
--* Last update: May 31th, 2021
--* Required reading time: 7 minutes
--
  == 1. Prerequisites ==
  * Basic knowledge of the eMagiz platform
@@ -12,93 +12,85 @@
  == 2. Key concepts ==
--This microlearning centers around learning how to process an incoming file per line.
++This microlearning centers around learning how to set up your volume mapping correctly 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.
--* 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 make sure that the docker container in your runtime(s) running has access to this path. There are several ways of dealing with this challenge. First, 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.
++* Volume
++* Bind mount
++* 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 first explain how to set up this configuration within eMagiz. Then, you must navigate to Deploy -> Architecture on the model level. In this overview, you can 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 and runtime-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 that is relevant for that runtime to read and/or write persistent data. To configure this type you need to link the runtime volume to a machine volume that you can create within the same pop-up. This means that you can re-use a "Machine volume" over multiple runtimes (i.e. containers).
--==== 3.1.1 Stax Event Item Reader ====
++So, at first we open the tab called "Machine volume". By pressing the "New" button we can define a new "Machine volume". In the pop-up that follows we can define the name of a machine volume and tell whether the volume already exists on your docker installation or not.
--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.
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--machine-volumes-configuration.png]]
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--stax-event-item-reader-config.png]]
++Once you have done so we press "Save" and switch back to the "Runtime volumes" tab. In here we press the "New" button to create a new "Runtime volume". In the pop-up that follows we first need to select the Type we want to use. For this example we use the type called "Volume". Based on your selection the relevant input fields will change.
--==== 3.1.2 Flat File Item Reader ====
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]]
--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
++The first thing we need to select is the "Machine volume". Once we have selected our "Machine volume" we need to select the Target that is 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 "Machine volume" name to arrive at the correct directory from which eMagiz needs to read data (or write data to). So in our case this would be "/file-directory/target."
--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).
++The last setting we need to configure is to define which rights we will grant our runtime on the volume we are creating. The default setting is read/write rights for the runtime which is sufficient in most cases. The result of following these steps will be the following.
--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.
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume-filled-in.png]]
--For the remainder of this microlearning, we will assume that the option pass through line mapper is chosen.
++{{warning}}Note, that when you use the Volume option the external system with which you exchange data on-premise via a file based method need to be able to write or read the data from the volume (i.e. directory) you have configured in Docker. Should this be a problem the Bind mount alternative discussed below should be considered.{{/warning}}
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--flat-file-item-reader-passthrough.png]]
++=== 3.2 Bind mount ===
--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.
++=== 3.3 Temporary file system ===
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--flat-file-item-reader-passthrough-advanced.png]]
++=== 3.4 Named pipe ===
--=== 3.2 Poller ===
--
--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:
--
--- Fixed Delay Trigger
--- Fixed Rate Trigger
--- Cron Trigger
--
--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.
--
--[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-processing-a-file-per-line--poller-config.png]]
--
--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.
--
  == 4. Assignment ==
--Configure an entry in which you define the component and configuration needed to process a file on a per-line basis.
++Configure an entry in which you build the archiving and the clean up of the archiving.
  This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
  == 5. Key takeaways ==
--* 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
++* Archiving is used for audit purposes
++* Archiving is used for retry scenarios
++* Ensure that data is cleaned after a retention period to keep in control of the data
++* Don't forget the max messages per poll
  == 6. Suggested Additional Readings ==
--There are no suggested additional readings on this topic
++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:
++* [[File Archiving>>doc:Main.eMagiz Store.Accelerators.File Archiving.WebHome||target="blank"]]
++* [[Delete Folder(s)>>doc:Main.eMagiz Store.Accelerators.Delete Folder(s).WebHome||target="blank"]]
++
  == 7. Silent demonstration video ==
  This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
--{{video attachment="novice-file-based-connectivity-processing-a-file-per-line.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
++{{video attachment="novice-file-based-connectivity-characterset.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
  )))((({{toc/}}))){{/container}}{{/container}}

Changes for page Volume Mapping (On-premise)

Summary

Details

Navigation