Changes for page Pick up Files

Last modified by Danniar Firdausy on 2024/08/21 16:48

From version 21.1
edited by Erik Bakker
on 2022/08/15 08:24
Change comment: There is no comment for this version
To version 22.1
edited by Eva Torken
on 2023/05/09 11:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -118,13 +118,8 @@
118 118  
119 119  With all this in mind, you have successfully learned how to set up your first connectivity via a messaging flow in eMagiz!
120 120  
121 -== 4. Assignment ==
121 +== 4. Key takeaways ==
122 122  
123 -Build an entry that retrieves files from an external source and ensures that the data is delivered on the onramp queue.
124 -This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment.
125 -
126 -== 5. Key takeaways ==
127 -
128 128  * Key considerations when picking up files are:
129 129   * What are the determining criteria to define when a file is "ready" to be picked up (age, pattern, size, etc.)
130 130   * With what frequency is eMagiz going to check for new files
... ... @@ -131,14 +131,8 @@
131 131   * Has eMagiz the appropriate rights to read from the directory where the messages are to be retrieved from
132 132   * What is the format (i.e. XML, JSON, EDI, TXT, CSV, etc.) of the files that eMagiz needs to retrieve
133 133  
134 -== 6. Suggested Additional Readings ==
129 +== 5. Suggested Additional Readings ==
135 135  
136 136  If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
137 137  
138 -== 7. Silent demonstration video ==
139 -
140 -This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
141 -
142 -{{video attachment="crashcourse-messaging-pick-up-files.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
143 -
144 144  )))((({{toc/}}))){{/container}}{{/container}}