Skip to Content
Last modified by Erik Bakker on 2023/01/31 10:18
From version 3.1
edited by Erik Bakker
on 2022/04/29 15:21
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 -REST - Request & Response
1 +eMagiz Long Term Archiving
Content
... ... @@ -1,18 +1,23 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 -(((**~1. How to use**
4 -With this store component, you can easily set up a connection to a REST endpoint using various authentication mechanisms while taking the response into account.
3 +(((
4 +== About ==
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.
5 5  
6 -**2. Keynotes & restrictions **
7 +== Documentation ==
7 7  
8 -a. Note that you need to select the valid authentication based on the requirement of the external system.
9 +==== 1. How to use====
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.
9 9  
10 -**3. License Information**
11 -Part of the standard license agreement as agreed upon when using the store for the first time.
12 +==== 2. Keynotes & restrictions====
12 12  
13 -**4. Relevant eMagiz Academy Microlearnings**
14 -[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]]
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.
15 15  
19 +==== 3. License Information====
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.
16 16  
17 17  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/?]])))
18 18  
... ... @@ -20,15 +20,8 @@
20 20  
21 21  ((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
22 22  |=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
23 -|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code
24 -|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth
25 -|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate
26 -|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper
27 -|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials
28 -|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL
29 -|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token
30 -|(% style="width:45px" %) h|(% style="width:241px" %) Token
31 -|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget)
28 +|(% style="width:45px" %) a|(% style="width:241px" %) XML message(s)
29 +|(% style="width:45px" %) b|(% style="width:241px" %) JSON Message(s)
32 32  )))
33 33  {{/container}}
34 34  {{/container}}