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 31.1
edited by Erik Bakker
on 2024/02/21 21:51
Change comment: Renamed back-links.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Data Sink
1 +Mendix - SFTP Data pipelines
Content
... ... @@ -2,31 +2,46 @@
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.
6 6  
6 +Data pipeline configuration inside an entry connector to transfer Mendix App object data to CSV files on SFTP server. This flow can also be used as starting point for other data pipeline integrations.
7 +
7 7  == Documentation ==
8 8  
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 +==== 1. How to use ====
11 11  
12 -==== 2. Keynotes & restrictions====
12 +With the help of this store item, you have a data pipeline configuration inside an entry connector to transfer Mendix App object data to CSV files on SFTP server.. This allows for the following:
13 +
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.
15 +* Reading data from Mendix using OData v3.
16 +* Convert data to flat files (CSV).
17 +* Writing data to SFTP.
18 +* Job dashboard (See Deploy -> Runtime Dashboard -> [Select Runtime] - > [Select Flow] -> Jobs ).
18 18  
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.
20 +==== 2. Keynotes & restrictions ====
21 21  
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/?]])))
22 +* Source data must be shared in Mendix using a 'Published OData service'. If applicable in the settings tab set the association configuration to 'As an associated object id'.
23 +* Mendix application must be reachable by the eMagiz runtime.
24 +* Before use, please rename job 'system.message.job' and step 'system.message.step1' to match your system and integration name. Make sure to update support.job-launch-request accordingly.
25 +* When using multiple pipeline flows on one runtime, an h2 'already in use' exception might occur. To prevent these errors please keep the name of the h2 database different for each flow on one runtime by renaming the 'dp.h2.message.database' deploy property in the "support.h2-database" component.
26 +* When you want to import the flow multiple times for one system, you should change the names of the following properties by replacing 'message' with the name of the message type of each integration:
27 +** dp.odata.message.cron (component: receive.cron)
28 +** dp.odata.message.url (component: system.message.job -> system.message.step1 -> Item reader)
29 +** dp.h2.message.database (component: support.h2-database)
30 +** dp.sftp.message.filename.prefix (component: transform.job-launch-request - > Expression)
23 23  
32 +==== 3. License Information ====
24 24  
34 +Part of the standard license agreement as agreed upon when using the store for the first time.
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)
36 +==== 4. Relevant eMagiz Academy Microlearnings ====
37 +
38 +* [[eMagiz Data pipelines>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.intermediate-data-pipelines-understanding-data-pipelines.WebHome||target="blank"]]
39 +
40 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]]//
30 30  )))
42 +
43 +(((
44 +
45 +)))
31 31  {{/container}}
32 32  {{/container}}