Skip to Content
Last modified by Erik Bakker on 2023/01/31 10:18
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 10.1
edited by Erik Bakker
on 2022/05/02 09:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Data Sink
1 +eMagiz Long Term Archiving
Content
... ... @@ -2,19 +2,19 @@
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 functionality, you can sink your messages into the eMagiz long-term archiving solution. Once the message is stored in the eMagiz long-term archiving solution, you will have the option to request a retrieval of the data at our support desk.
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 +Once stored, eMagiz can retrieve for a period of multiple years in chunks after you submit a request for retrieval at our support desk. In the meantime, the data is kept safely for legal and auditory purposes.
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 you should think about when you want to archive your data to the eMagiz long-term archiving. 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 archive behavior to happen before the actual processing. If the archiving 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 long-term archiving solution 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 archiving to make this functionality work.
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.