Skip to Content

Changes for page Routing - SpEL

Last modified by Erik Bakker on 2023/01/31 12:09
From version 15.1
edited by eMagiz
on 2022/06/17 12:32
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 -Routing - SpEL
1 +SOAP Web service Connectivity
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,31 +2,40 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  == About ==
5 -With the help of this SpEL expression, you can easily route your asynchronous messages via your messaging integrations according to the best practice.
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 SpEL expression, you can easily route your asynchronous messages via your messaging integrations according to the best practice.
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 an example of how you can use the SpEL expression within eMagiz.
15 -* The key element of this SpEL expression is that it combines the values of two input headers into a list of possible outcomes to which you can route messages.
16 -* Note that this store item only defines the SpEL expression portion of the routing. The remainder should be created by you.
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.
17 17  
18 18  ==== 3. License Information====
19 19  Part of the standard license agreement as agreed upon when using the store for the first time.
20 20  
21 21  ==== 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]]
22 22  
23 -[[SPEL Expressions>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Handling.advanced-data-handling-spel-expressions.WebHome||target="blank"]]
24 -[[https:~~/~~/regex101.com/>>url:https://regex101.com/]]
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/?]])))
24 +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 -((()))
28 +((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
29 +|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
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
39 +)))
31 31  {{/container}}
32 32  {{/container}}