Skip to Content
Last modified by Eva Torken on 2024/02/21 21:34
From version 41.1
edited by Carlijn Kokkeler
on 2022/10/05 13:00
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.CarlijnKokkeler
1 +XWiki.etorken
Content
... ... @@ -42,14 +42,10 @@
42 42   attributeFormDefault="unqualified" elementFormDefault="unqualified"
43 43   targetNamespace="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/">
44 44  {{/code}}
45 -<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
46 -<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
47 - xmlns="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/"
48 - attributeFormDefault="unqualified" elementFormDefault="unqualified"
49 - targetNamespace="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/">
50 50  
51 51  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:
52 52  
48 +{{code language="xml"}}
53 53  <xs:complexType name="Input">
54 54   <xs:sequence>
55 55   <xs:element name="String" type="nonEmptyString"/>
... ... @@ -74,9 +74,11 @@
74 74   <xs:enumeration value="PLANNING"/>
75 75   </xs:restriction>
76 76   </xs:simpleType>
73 +{{/code}}
77 77  
78 78  To wrap things up you need to define your Request and Response element and close the schema:
79 79  
77 +{{code language="xml"}}
80 80  <xs:element name="SendNptRequest">
81 81   <xs:complexType>
82 82   <xs:sequence>
... ... @@ -88,6 +88,7 @@
88 88   <xs:complexType/>
89 89   </xs:element>
90 90   </xs:schema>
89 +{{/code}}
91 91  
92 92  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.
93 93  
... ... @@ -97,13 +97,8 @@
97 97  
98 98  With this done you have successfully added validation to your SOAP web service.
99 99  
100 -== 4. Assignment ==
99 +== 4. Key takeaways ==
101 101  
102 -Add validation to the SOAP Webservice we have been configuring.
103 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
104 -
105 -== 5. Key takeaways ==
106 -
107 107  * Crucial parts in the configuration are:
108 108   ** Operation Name
109 109   ** SOAP Webservice Namespace
... ... @@ -113,12 +113,8 @@
113 113  * The WSDL is used for external documentation
114 114  * Use the XSD generated by eMagiz based on the system message as a starting point
115 115  
116 -== 6. Suggested Additional Readings ==
110 +== 5. Suggested Additional Readings ==
117 117  
118 118  If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
119 119  
120 -== 7. Silent demonstration video ==
121 -
122 -{{video attachment="novice-soap-webservice-connectivity-validate-incoming-messages.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
123 -
124 124  )))((({{toc/}}))){{/container}}{{/container}}