Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:39
From version 34.1
edited by Erik Bakker
on 2022/06/12 09:34
Change comment: There is no comment for this version
To version 48.1
edited by Eva Torken
on 2023/06/27 11:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Configure your SOAP web service
1 +Validate Incoming Messages
Parent
... ... @@ -1,1 +1,1 @@
1 -WebHome
1 +Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,11 +1,8 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -When setting up a point at which your customers can talk to you eMagiz offers various methods of creating such a point. One of those options is by hosting a SOAP Webservice in eMagiz that handles XML messages asynchronously or synchronously. In this microlearning, we will learn the basics of this configuration in the various phases of the platform so you can easily set up your SOAP web service.
2 +When setting up a point at which your customers can talk to you, eMagiz offers various methods of creating such a point. One of those options is to host a SOAP Webservice in eMagiz that handles XML messages asynchronously or synchronously. In this microlearning, we will zoom in on the part that validation of the messages plays when offering such a SOAP web service.
3 3  
4 -Should you have any questions, please contact academy@emagiz.com.
4 +If you have any questions, don't hesitate to contact academy@emagiz.com.
5 5  
6 -* Last update: June 10th, 2021
7 -* Required reading time: 7 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  * Basic knowledge of the eMagiz platform
11 11  
... ... @@ -12,7 +12,7 @@
12 12  == 2. Key concepts ==
13 13  This microlearning centers around configuring your SOAP web service.
14 14  
15 -By configuring, we mean: Designing and determining the characteristics of the SOAP web service
12 +By configuring, we mean: Designing and determining the characteristics of the SOAP web service.
16 16  
17 17  Crucial parts in the configuration are:
18 18  * Operation Name
... ... @@ -20,12 +20,12 @@
20 20  * Validation
21 21  * Authentication
22 22  
23 -Of these four points, the last two will be discussed in separate microlearnings.
24 -
25 -== 3. Configure your SOAP Webservice ==
20 +Of these four points, we will zoom in on the validation part of our SOAP Webservice in this microlearning.
26 26  
27 -When setting up a point at which your customers can talk to you eMagiz offers various methods of creating such a point. One of those options is by hosting a SOAP Webservice in eMagiz that handles XML messages asynchronously or synchronously. In this microlearning, we will learn the basics of this configuration in the various phases of the platform so you can easily set up your SOAP web service.
22 +== 3. Validate Incoming Messages ==
28 28  
24 +When setting up a point at which your customers can talk to you, eMagiz offers various methods of creating such a point. One of those options is to host a SOAP Webservice in eMagiz that handles XML messages asynchronously or synchronously. In this microlearning, we will zoom in on the part that validation of the messages plays when offering such a SOAP web service.
25 +
29 29  Crucial parts in the configuration are:
30 30  * Operation Name
31 31  * SOAP Webservice Namespace
... ... @@ -32,52 +32,28 @@
32 32  * Validation
33 33  * Authentication
34 34  
35 -Of these four points, the last two will be discussed in separate microlearnings. In this microlearning, we will focus on the first two aspects of the configuration. As you might have noticed I did not mention the fact whether the integration is synchronous or asynchronous as a crucial part of the configuration. The reason being that when configuring a (SOAP) web service you always need to send an acknowledgment back to the client calling the web service to let them know what the status of the message is. In case you want to set up the rest of your integration asynchronously you can send an empty message back as acknowledgment. In case you want to set up the rest of your integration synchronously you need to send the response you have received from the backend operation back to the client. More on the choice between asynchronous and synchronous in a later stage.
32 +Of these four points, we will zoom in on the validation part of our SOAP Webservice in this microlearning. The SOAP Webservice serves as a point of entry where people with the proper credentials (security) and the correct answers (validation) can enter and perform their actions. In the previous microlearning, we talked about the validation part. In this microlearning, we talk about the security part.
36 36  
37 -=== 3.1 Operation Name ===
34 +=== 3.1 Configuration on system message level in Design ===
38 38  
39 -Let us first zoom in on the parts of the configuration before we learn how you can implement it in eMagiz. Starting with the operation name. When you have dealt with the API Gateway offering of eMagiz in the past or have some knowledge of how APIs work the notion of an operation name should not be unfamiliar. In essence, it is a unique name that defines a certain operation. In eMagiz the best practice for naming the operation is as follows:
36 +As you have learned from the crash course, you can validate an XML message with the help of an XSD. This XSD describes data types, order, associations, and length of attributes. You can use such an XSD to validate what your clients send you. eMagiz will automatically define a WSDL based on the combination of system messages you provide for each operation you want to host. To ensure that the WSDL is created correctly, don't forget to add an entity called "Send{givenname}Request" to the (request) system message and an entity called "Send{givenname}Response" in case you have a response system message. An example of how this needs to be configured in Design is shown below.
40 40  
41 -* Send{technicalnameoftheoperation}
38 +[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--root-entity-for-wsdl.png]]
42 42  
43 -When you are in Create you will notice that eMagiz uses the default suffix of Request and Response is added to the operation name. Therefore the full operation name a client needs to call to get the desired result if you adhere to the best practice is:
40 +=== 3.2 Effect in Create ===
44 44  
45 -* Send{technicalnameoftheoperation}Request
42 +In the infra flow, eMagiz automatically adds a support object of the "Dynamic WSDL" type. In this support object, the link is made between the system message definitions and the WSDL that will be created based on this.
46 46  
47 -=== 3.2 SOAP Webservice Namespace ===
44 +[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--dynamic-wsdl-support-object-infra.png]]
48 48  
49 -The second part of the configuration is the SOAP Webservice Namespace. When hosting a SOAP Webservice via the standard eMagiz tooling you need to define a namespace. To smoothen this process eMagiz automatically generates a namespace based on the configuration settings you choose in the Design phase of eMagiz.
46 +{{warning}}Note that when you make changes to the system message after the integration is already in Create, or when you add a new integration to Create, you need to create a new version of your infra flow to be able to deploy the changes to your WSDL.{{/warning}}
50 50  
51 -=== 3.3 Configuration in eMagiz ===
48 +With this done, you have successfully added validation to your SOAP web service.
52 52  
53 -Now that we know what configurations are required, we can see how we can implement this in eMagiz. In the Capture phase, nothing changes. You simply draw a system on the canvas including at least one line that goes from the system towards eMagiz. When you are done you move to the Design phase in eMagiz. In this phase, you need to correctly set up the operation name(s) and the SOAP Webservice Namespace.
54 -
55 -The configuration in Design starts at the system level. At the system level, you need to define the technical name (or let eMagiz automatically fill it in for you) and select the checkbox called Combined Entry Connector. By selecting this checkbox you tell eMagiz that you want to host an endpoint for others to call.
56 -
57 -[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-configure-your-soap-webservice--combined-entry-check.png]]
58 -
59 -As you can see, selecting this option opens up a new choice to make. In this case between SOAP Webservice and Custom.
60 -
61 -[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-configure-your-soap-webservice--combined-entry-choice.png]]
62 -
63 -In this case, we opt for the SOAP web service. After you have done so eMagiz will automatically define the SOAP Webservice Name and SOAP Webservice Namespace.
64 -
65 -[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-configure-your-soap-webservice--combined-entry-soap-ws-namespace.png]]
66 -
67 -With this, you are done with your configuration on the system level. Don't forget to update the status of your task. Now that we have configured the system it is time to configure the integration that is drawn from the system to eMagiz. We can do so by double-clicking on it (or by accessing the context menu and selecting the edit option). When you open the Edit page on the integration level you will notice that a new segment is added (compared to other integrations). This segment defines the settings on the system level we have just specified and defines the operation name.
68 -
69 -[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-configure-your-soap-webservice--edit-integration.png]]
70 -
71 -As you can see eMagiz has already prefilled the operation name for you based on the best practice at eMagiz. If you want to change you have the option to do so. Do note that for the sake of consistency it would be smart to use the same naming convention within a single project to avoid confusion.
72 -
73 -=== 3.4 Add integration to Create ===
74 -
75 -Now that we have finished the configuration in Design the last step of this microlearning is to add the integration to Create. You can simply do so by navigating to Create -> Add integrations and selecting the integration to move it to Create. After you have selected it press Save to add the integration to Create.
76 -
77 77  == 4. Assignment ==
78 78  
79 -Configure a SOAP web service that consists of at least one operation and add it to Create.
80 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
52 +Add validation to the SOAP Webservice we have been configuring.
53 +This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment.
81 81  
82 82  == 5. Key takeaways ==
83 83  
... ... @@ -86,14 +86,17 @@
86 86   ** SOAP Webservice Namespace
87 87   ** Validation
88 88   ** Authentication
89 -* For ease, you can use the default naming convention of eMagiz
62 +* Validation is done with the help of an XSD
63 +* The WSDL is used for external documentation
64 +* eMagiz will automatically generate the WSDL for you based on your system messages
65 +** Do not forget to add the correct root entity to your system message to make the WSDL work
90 90  
91 91  == 6. Suggested Additional Readings ==
92 92  
93 -If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
69 +If you are interested in this topic and want more information, please read the help text provided by eMagiz.
94 94  
95 95  == 7. Silent demonstration video ==
96 96  
97 -{{video attachment="novice-soap-webservice-connectivity-configure-your-soap-webservice.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
73 +{{video attachment="novice-soap-webservice-connectivity-validate-incoming-messages-gen3.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
98 98  
99 99  )))((({{toc/}}))){{/container}}{{/container}}