Changes for page Mendix -> Redshift - Data Pipeline
Last modified by Erik Bakker on 2024/02/21 21:51
From version 18.1
edited by Erik Bakker
on 2022/05/02 11:10
on 2022/05/02 11:10
Change comment:
There is no comment for this version
To version 5.1
edited by Erik Bakker
on 2022/05/02 08:20
on 2022/05/02 08:20
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - DeltaService- Data Pipeline1 +SOAP Web service Connectivity - Content
-
... ... @@ -1,33 +1,40 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 -= =About ==5 - Datapipelineconfigurationinsideanentryconnectorthatcreatesacustom Deltaview onyourcompletetable. Notethatthisflowonly holdsthelogictocreateaDelta based ona full load. Theactualretrievalofthefull-loadand sendingthedata to anotherprocessineMagizare notpart of thestoreitem.4 += About = 5 +This store element will allow you to create an easy connection to SOAP based web services. XML data can be send to these web services, and for each connectivity type there is a Flow Fragment available. 6 6 7 -= =Documentation ==7 += Documentation = 8 8 9 -==== 1. How to use==== 10 -With the help of this store item, you have a data pipeline configuration inside an entry connector that creates a custom Delta view on your complete table. This allows for the following: 11 - 12 -* Creating a delta from a full load. 9 + **~1. How to use** 10 +Ensure to locate the right connectivity method and import the right flow fragment. 13 13 14 - ====2. Keynotes & restrictions====12 +**2. Keynotes & restrictions ** 15 15 16 -* The store component only provides the logic to create a delta from a full-load. 17 -* The store component does not provide the retrieval of the full load nor does it provide guidance on how to send the delta information to other parts of the solution. 18 -* Using this functionality is an expert functionality as it requires quite some context on how databases work and how eMagiz works 14 +a. These flow fragments will contain only the eMagiz components to make a call out to the SOAP based webservice - These components do not hold any system messages - The basic authentication flow fragment requires empty key and trust store that are to be added separately. These are not included in this store component. 19 19 20 - ====3. License Information====16 +**3. License Information** 21 21 Part of the standard license agreement as agreed upon when using the store for the first time. 22 22 23 -==== 4. Relevant eMagiz Academy Microlearnings==== 19 +**4. Relevant eMagiz Academy Microlearnings** 20 +[[https:~~/~~/emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice>>url:https://emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice]] 24 24 25 -[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-data-pipelines-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-data-pipelines-index]] 26 26 27 - //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/?]])))23 +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/?]]))) 28 28 29 29 30 30 31 -((())) 27 +((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 28 +|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 29 +|(% style="width:45px" %) a|(% style="width:241px" %) Basic Authentication 30 +|(% style="width:45px" %) b|(% style="width:241px" %) WS Addressing - Call back 31 +|(% style="width:45px" %) c|(% style="width:241px" %) Client certificate 32 +|(% style="width:45px" %) d|(% style="width:241px" %) Mapped headers 33 +|(% style="width:45px" %) e|(% style="width:241px" %) Token based - static 34 +|(% style="width:45px" %) f|(% style="width:241px" %) Token based - dynamic 35 +|(% style="width:45px" %) g|(% style="width:241px" %) SSL 36 +|(% style="width:45px" %) h|(% style="width:241px" %) No authentication 37 +|(% style="width:45px" %) i|(% style="width:241px" %) Dynamic URL 38 +))) 32 32 {{/container}} 33 33 {{/container}}