Skip to Content
Last modified by Erik Bakker on 2024/02/21 21:51
From version 9.1
edited by Erik Bakker
on 2022/05/02 09:34
Change comment: There is no comment for this version
To version 13.1
edited by Erik Bakker
on 2022/05/02 09:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Data Sink
1 +Read ZIP
Content
... ... @@ -2,31 +2,31 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  == About ==
5 -With the help of this functionality, you can sink your messages into the eMagiz data sink bucket. Once the message is stored in the eMagiz data sink bucket, you will have the option to view this message in the Manage phase.
5 +With the help of this store item, you can read zip files with the help of several custom Groovy scripts to unzip and further process them.
6 6  
7 7  == Documentation ==
8 8  
9 9  ==== 1. How to use====
10 -Once stored, eMagiz can retrieve all messages with the same ID attached during the sink action via the Manage phase. In this case, it is assumed that your eMagiz data sink is such that you can review them on the fly. Other eMagiz data sink variants are offered that required specific on-demand queries.
10 +With the help of this store item, you can read zip files with the help of several custom Groovy scripts to unzip and further process them.
11 11  
12 12  ==== 2. Keynotes & restrictions====
13 13  
14 -* Note that you should think about when you want to archive your data to the eMagiz data sink. That choice determines what the impact on the functional flow is.
15 -* Don't use a wiretap to invoke this part of the flow, as that causes the sink's behavior to happen before the actual processing. If the sink fails, the message will not be delivered via the functional part of the flow.
16 -* Note that we define (among others) how the message is stored in the data sink bucket in this component. The file structure expression should not be altered, as changing this would break the functionality.
17 -* Note that the 'standard' eMagiz headers to define the source system (i.e. relevant systems) and the messageType need to be available upon sinking to make this functionality work.
14 +* Note that this is a custom Groovy script that works on the current infrastructure of eMagiz.
15 +* Any custom additions that are needed for your specific use cases need to be created by you and eMagiz will not create it for you.
16 +* The headers in the header component need to match the names on the third line of the groovy script
17 +* Please check out the following link to learn a bit more about Groovy: https://www.tutorialspoint.com/groovy/index.htm
18 18  
19 19  ==== 3. License Information====
20 20  To use this store item you need to secure an additional license on the eMagiz platform. If you are interested in such a license please contact us at productmanagement@emagiz.com.
21 21  
22 +==== 4. Relevant eMagiz Academy Microlearnings====
23 +
24 +None
25 +
22 22  Would you please consult the privacy policy of eMagiz at the following link: [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))
23 23  
24 24  
25 25  
26 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
27 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
28 -|(% style="width:45px" %) a|(% style="width:241px" %) XML message(s)
29 -|(% style="width:45px" %) b|(% style="width:241px" %) JSON Message(s)
30 -)))
30 +((()))
31 31  {{/container}}
32 32  {{/container}}