Changes for page Mendix -> Redshift - Data Pipeline
Last modified by Erik Bakker on 2024/02/21 21:51
From version 10.1
edited by Erik Bakker
on 2022/05/02 09:37
on 2022/05/02 09:37
Change comment:
There is no comment for this version
To version 17.2
edited by Erik Bakker
on 2022/05/02 11:08
on 2022/05/02 11:08
Change comment:
Update document after refactoring.
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -e MagizDataSink1 +Delta Service - Data Pipeline - Content
-
... ... @@ -2,35 +2,29 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 -With the help of this functionality, you can sinkyour messagesintotheeMagiz dataink bucket.Once the messageis stored inthe eMagizdata sink bucket,youwillhave the optionto viewthis messagein theManage phase.5 +With the help of this transformation, you can easily wrap the body of your message in CDATA tags. This is sometimes needed to call an external web service. 6 6 7 7 == Documentation == 8 8 9 9 ==== 1. How to use==== 10 - Once stored, eMagiz can retrieve all messages with thesameIDattached duringthe sinkactionviathe Managephase. In thiscase,itis assumedthatyour eMagizdatainkis suchthat you can reviewthem onthefly. OthereMagizdatasink variantsareoffered thatrequiredspecificon-demand queries.10 +With the help of this transformation, you can easily wrap the body of your message in CDATA tags. This is sometimes needed to call an external web service. 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 XSLT that is designed for a specific cause. 15 +* Always try to understand the context before you implement this transformation. 18 18 19 19 ==== 3. License Information==== 20 - To use this store itemyouneedto secureanadditionallicenseon the eMagiz platform.Ifyouareinterestedinsucha licensepleasecontactusatproductmanagement@emagiz.com.18 +Part of the standard license agreement as agreed upon when using the store for the first time. 21 21 22 22 ==== 4. Relevant eMagiz Academy Microlearnings==== 23 23 24 - [[https:~~/~~/emagiz.github.io/docs/microlearning/advanced-data-management-data-sink>>url:https://emagiz.github.io/docs/microlearning/advanced-data-management-data-sink]]22 +None 25 25 26 -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/?]]))) 24 +//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/?]]))) 27 27 28 28 29 29 30 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 31 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 32 -|(% style="width:45px" %) a|(% style="width:241px" %) XML message(s) 33 -|(% style="width:45px" %) b|(% style="width:241px" %) JSON Message(s) 34 -))) 28 +((())) 35 35 {{/container}} 36 36 {{/container}}