Skip to Content
Last modified by Eva Torken on 2024/02/21 21:34
From version 40.1
edited by Erik Bakker
on 2022/08/22 15:38
Change comment: There is no comment for this version
To version 43.2
edited by Eva Torken
on 2024/02/21 21:34
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -WebHome
1 +Main.eMagiz Academy.Microlearnings.Legacy Functionality.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -35,14 +35,17 @@
35 35  
36 36  What eMagiz does need from you is the correct XSD for validation. As a starting point you should download the XSD that eMagiz has generated based on the system message(s) you have defined in the Design phase. Once you have that you can structure the XSD correctly. A valid XSD start with a schema segment. In this segment you need to define your SOAP WS namespace:
37 37  
38 +{{code language="xml"}}
38 38  <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
39 39  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
40 40   xmlns="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/"
41 41   attributeFormDefault="unqualified" elementFormDefault="unqualified"
42 42   targetNamespace="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/">
44 +{{/code}}
43 43  
44 44  Once you have that you need to copy all complex and simple types from the XSD that you downloaded and paste them below the lines you have created:
45 45  
48 +{{code language="xml"}}
46 46  <xs:complexType name="Input">
47 47   <xs:sequence>
48 48   <xs:element name="String" type="nonEmptyString"/>
... ... @@ -67,9 +67,11 @@
67 67   <xs:enumeration value="PLANNING"/>
68 68   </xs:restriction>
69 69   </xs:simpleType>
73 +{{/code}}
70 70  
71 71  To wrap things up you need to define your Request and Response element and close the schema:
72 72  
77 +{{code language="xml"}}
73 73  <xs:element name="SendNptRequest">
74 74   <xs:complexType>
75 75   <xs:sequence>
... ... @@ -81,6 +81,7 @@
81 81   <xs:complexType/>
82 82   </xs:element>
83 83   </xs:schema>
89 +{{/code}}
84 84  
85 85  Combining this will result in a valid XSD for my example. In your case, you will need to enter other values. When you are done with the creation of the XSD save it with a name such as spwbsrv-connector.xsd and upload it to the flow. After you have uploaded the XSD link it to the connector-xsd support object in your entry.
86 86  
... ... @@ -90,13 +90,8 @@
90 90  
91 91  With this done you have successfully added validation to your SOAP web service.
92 92  
93 -== 4. Assignment ==
99 +== 4. Key takeaways ==
94 94  
95 -Add validation to the SOAP Webservice we have been configuring.
96 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
97 -
98 -== 5. Key takeaways ==
99 -
100 100  * Crucial parts in the configuration are:
101 101   ** Operation Name
102 102   ** SOAP Webservice Namespace
... ... @@ -106,12 +106,8 @@
106 106  * The WSDL is used for external documentation
107 107  * Use the XSD generated by eMagiz based on the system message as a starting point
108 108  
109 -== 6. Suggested Additional Readings ==
110 +== 5. Suggested Additional Readings ==
110 110  
111 111  If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
112 112  
113 -== 7. Silent demonstration video ==
114 -
115 -{{video attachment="novice-soap-webservice-connectivity-validate-incoming-messages.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
116 -
117 117  )))((({{toc/}}))){{/container}}{{/container}}