Wiki source code of Mendix - SFTP Data pipelines

Last modified by Erik Bakker on 2024/02/21 21:51

Hide last authors
Erik Bakker 2.1 1 {{container}}
2 {{container layoutStyle="columns"}}
Erik Bakker 4.1 3 (((
Erik Bakker 31.1 4 == About ==
eMagiz 27.1 5
Erik Bakker 26.1 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.
Erik Bakker 4.1 7
Erik Bakker 7.1 8 == Documentation ==
Erik Bakker 4.1 9
Erik Bakker 31.1 10 ==== 1. How to use ====
11
Erik Bakker 26.1 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:
Erik Bakker 18.1 13
Erik Bakker 31.1 14
Erik Bakker 24.1 15 * Reading data from Mendix using OData v3.
Erik Bakker 26.1 16 * Convert data to flat files (CSV).
17 * Writing data to SFTP.
Erik Bakker 22.1 18 * Job dashboard (See Deploy -> Runtime Dashboard -> [Select Runtime] - > [Select Flow] -> Jobs ).
Erik Bakker 2.1 19
Erik Bakker 31.1 20 ==== 2. Keynotes & restrictions ====
Erik Bakker 2.1 21
Erik Bakker 25.1 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.
Erik Bakker 19.1 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:
Erik Bakker 31.1 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)
Erik Bakker 3.1 31
Erik Bakker 31.1 32 ==== 3. License Information ====
33
Erik Bakker 15.1 34 Part of the standard license agreement as agreed upon when using the store for the first time.
Erik Bakker 2.1 35
Erik Bakker 31.1 36 ==== 4. Relevant eMagiz Academy Microlearnings ====
Erik Bakker 10.1 37
Erik Bakker 31.1 38 * [[eMagiz Data pipelines>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.intermediate-data-pipelines-understanding-data-pipelines.WebHome||target="blank"]]
Erik Bakker 2.1 39
Erik Bakker 31.1 40 //Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]]//
41 )))
42
43 (((
44
45 )))
Erik Bakker 2.1 46 {{/container}}
47 {{/container}}