Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:39
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 42.2
edited by Erik Bakker
on 2022/12/30 11:48
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Validate Incoming Messages
1 +novice-soap-webservice-connectivity-validate-incoming-messages-gen3
Parent
... ... @@ -1,1 +1,1 @@
1 -WebHome
1 +Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome
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