Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:39
From version 45.1
edited by Erik Bakker
on 2022/12/30 12:12
Change comment: There is no comment for this version
To version 49.1
edited by Eva Torken
on 2023/06/27 11:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -29,7 +29,7 @@
29 29  * Validation
30 30  * Authentication
31 31  
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 security part. In this microlearning, we talk about the validation part.
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.
33 33  
34 34  === 3.1 Configuration on system message level in Design ===
35 35  
... ... @@ -45,23 +45,14 @@
45 45  
46 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}}
47 47  
48 -In this same support object, you also see the default location of the hosted SOAP endpoint, which is http://localhost:${entry.connector.ws.port}/ws/{soap WS name}/. Based on this, you can find the WSDL by adding {soap WS name}.wsdl to the URI. In this example, when hosting the SOAP web service on-premise, a valid URI would be "http://localhost:8099/ws/soapgn3-connector/soapgn3-connector.wsdl".
49 -
50 -{{info}}Note that when running your web service in the eMagiz cloud, the first part (the host part) will change depending on your configuration in Deploy Architecture and the cloud slot on which you are running. An example URI, in that case, would be "https://soap-test-cloud0000.emagizcloud.com/ws/soapgn3-connector/soapgn3-connector.wsdl"{{/info}}
51 -
52 52  With this done, you have successfully added validation to your SOAP web service.
53 53  
54 -== 4. Assignment ==
50 +== 4. Key takeaways ==
55 55  
56 -Add validation to the SOAP Webservice we have been configuring.
57 -This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment.
58 -
59 -== 5. Key takeaways ==
60 -
61 61  * Crucial parts in the configuration are:
62 62   ** Operation Name
63 63   ** SOAP Webservice Namespace
64 - ** validationvalidation
55 + ** Validation
65 65   ** Authentication
66 66  * Validation is done with the help of an XSD
67 67  * The WSDL is used for external documentation
... ... @@ -68,12 +68,8 @@
68 68  * eMagiz will automatically generate the WSDL for you based on your system messages
69 69  ** Do not forget to add the correct root entity to your system message to make the WSDL work
70 70  
71 -== 6. Suggested Additional Readings ==
62 +== 5. Suggested Additional Readings ==
72 72  
73 73  If you are interested in this topic and want more information, please read the help text provided by eMagiz.
74 74  
75 -== 7. Silent demonstration video ==
76 -
77 -{{video attachment="novice-soap-webservice-connectivity-validate-incoming-messages-gen3.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
78 -
79 79  )))((({{toc/}}))){{/container}}{{/container}}