Skip to Content

Changes for page Add SOAP Structure

Last modified by Erik Bakker on 2024/05/07 09:23
From version 19.1
edited by Erik Bakker
on 2022/05/02 10:20
Change comment: There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2022/05/02 09:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -XSLT Extension Gateway
1 +SOAP Web service Connectivity
Content
... ... @@ -2,31 +2,39 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  == About ==
5 -With the help of this store item, you can easily set up an XSLT extension Gateway. Note that the store item is illustrative in nature of how the functionality works and that you should change the XSLT and add additional logic to make it function completely.
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 -With the help of this store item, you can easily set up an XSLT extension Gateway. Note that the store item is illustrative in nature of how the functionality works and that you should change the XSLT and add additional logic to make it function completely.
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 this is a custom XSLT that is designed for a specific cause.
15 -* Always try to understand the context before you implement this transformation.
16 -* Change the XSLT (Extension Gateway) to reflect your needs when developing this functionality.
17 -* Note that the Password and Username parameters and accompanying properties are illustrative in nature and should be evaluated when implementing the functionality.
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.
18 18  
19 19  ==== 3. License Information====
20 20  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====
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]]
23 23  
24 -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/?]])))
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/?]])))
27 27  
28 28  
29 29  
30 -((()))
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 +)))
31 31  {{/container}}
32 32  {{/container}}