Skip to Content

Changes for page Add SOAP Structure

Last modified by Erik Bakker on 2024/05/07 09:23
From version 7.1
edited by Erik Bakker
on 2022/05/02 09:02
Change comment: There is no comment for this version
To version 24.1
edited by Erik Bakker
on 2024/02/21 21:34
Change comment: Renamed back-links.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SOAP Web service Connectivity
1 +Add SOAP Structure
Content
... ... @@ -2,39 +2,36 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 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  
6 +With the help of this transformation, you can easily add a SOAP structure (i.e. Envelope and Body) to your message. This is sometimes needed to communicate with an external system.
7 +
7 7  == Documentation ==
8 8  
9 -==== 1. How to use====
10 -Ensure to locate the right connectivity method and import the right flow fragment.
10 +==== 1. How to use ====
11 11  
12 -==== 2. Keynotes & restrictions====
12 +With the help of this transformation, you can easily add a SOAP structure (i.e. Envelope and Body) to your message. This is sometimes needed to communicate with an external system.
13 13  
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.
14 +==== 2. Keynotes & restrictions ====
15 15  
16 -==== 3. License Information====
16 +* Note that this is a custom XSLT that is designed for a specific cause.
17 +* Always try to understand the context before you implement this transformation.
18 +
19 +==== 3. License Information ====
20 +
17 17  Part of the standard license agreement as agreed upon when using the store for the first time.
18 18  
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]]
23 +==== 4. Relevant eMagiz Academy Microlearnings ====
21 21  
25 +* [[Configure your SOAP web service>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.novice-soap-webservice-connectivity-configure-your-soap-webservice.WebHome||target="blank"]]
26 +* [[SOAP Headers>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.novice-soap-webservice-connectivity-soap-headers||target="blank"]]
22 22  
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 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]]//
29 +)))
24 24  
25 25  
26 26  
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
33 +(((
34 +
38 38  )))
39 39  {{/container}}
40 40  {{/container}}