Changes for page Processing a File per Line
Last modified by Erik Bakker on 2024/08/26 12:29
From version 33.1
edited by Erik Bakker
on 2023/01/23 08:25
on 2023/01/23 08:25
Change comment:
There is no comment for this version
To version 31.1
edited by Erik Bakker
on 2022/08/22 14:17
on 2022/08/22 14:17
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -46,9 +46,9 @@ 46 46 ==== 3.1.2 Flat File Item Reader ==== 47 47 48 48 For the Flat File item reader, there are some more choices and configurations to be made. There are three options you can choose from: 49 - *Pass through line mapper50 - *Default line mapper51 - *Pattern matching composite line mapper49 +- Pass through line mapper 50 +- Default line mapper 51 +- Pattern matching composite line mapper 52 52 53 53 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). 54 54 ... ... @@ -66,9 +66,9 @@ 66 66 67 67 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: 68 68 69 - *Fixed Delay Trigger70 - *Fixed Rate Trigger71 - *Cron Trigger69 +- Fixed Delay Trigger 70 +- Fixed Rate Trigger 71 +- Cron Trigger 72 72 73 73 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. 74 74