Skip to Content

Changes for page Regex Match - SpEL

Last modified by Erik Bakker on 2023/01/31 10:28
From version 10.1
edited by Erik Bakker
on 2022/05/02 09:37
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2022/05/02 09:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Data Sink
1 +SOAP Web service Connectivity
Content
... ... @@ -2,26 +2,24 @@
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.
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 7  == Documentation ==
8 8  
9 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 +Ensure to locate the right connectivity method and import the right flow fragment.
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 +* These flow fragments will contain only the eMagiz components to make a call to a SOAP based webservice.
15 +* 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.
18 18  
19 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.
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====
21 +[[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]]
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]]
25 25  
26 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/?]])))
27 27  
... ... @@ -29,8 +29,15 @@
29 29  
30 30  ((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
31 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)
30 +|(% style="width:45px" %) a|(% style="width:241px" %) Basic Authentication
31 +|(% style="width:45px" %) b|(% style="width:241px" %) WS Addressing - Call back
32 +|(% style="width:45px" %) c|(% style="width:241px" %) Client certificate
33 +|(% style="width:45px" %) d|(% style="width:241px" %) Mapped headers
34 +|(% style="width:45px" %) e|(% style="width:241px" %) Token based - static
35 +|(% style="width:45px" %) f|(% style="width:241px" %) Token based - dynamic
36 +|(% style="width:45px" %) g|(% style="width:241px" %) SSL
37 +|(% style="width:45px" %) h|(% style="width:241px" %) No authentication
38 +|(% style="width:45px" %) i|(% style="width:241px" %) Dynamic URL
34 34  )))
35 35  {{/container}}
36 36  {{/container}}