...
| Note | ||
|---|---|---|
| ||
Use the WSDL and SoapUI to test your own Web Service Calls
|
| Info |
|---|
*SoapUI Is not required to perform Web Service Calls, however this can aid significantly in interpreting the WSDL and understanding the information requirements of each call. Other Possible Applications
*Using non-SOAP specific applications will require additional Configuration. |
Web Service Schema
Below is an XSD Schema which will inform you of the requirements of every Call
http://support-ws.azurewebsites.net/Data/ChainIT/DataService.svc?xsd=xsd0
Making a Web Service Call
To make a call you will need to know 3 thinks
Where you are sending the information?
- UAT Endpoint: https://bau-uat-ws.azurewebsites.net/Data/ChainIT/DataService.svc
- Production Endpoint: https://enodo-ws.azurewebsites.net/Data/ChainIT/DataService.svc
What you are planning to do?
i.e What function are you calling?
- Headers:
- Key: Content-Type Value: text/xml
- Key: SoapAction Value: <Insert Required SOAPAction from WSDL> (e.g. http://www.opensys.com.au/ChainIT/4.0/ChainITDataServices/IChainITService/Login)
| Info |
|---|
*SoapUI automatically configures the "Header" based on the call being made. However for other applications it is critical the correct SoapAction Url is entered in to make the correct call |
What information you are sending
...
| Code Block | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cha="http://www.opensys.com.au/ChainIT/4.0/ChainITDataServices">
<soapenv:Header/>
<soapenv:Body>
<!-- Requirements of each soapAction can be found http://support-ws.azurewebsites.net/Data/ChainIT/DataService.svc?xsd=xsd0 -->
<!-- Example XSD Schema available for Login
<xs:element name="Login">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="userName" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="password" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
Example XSD Schema available for Login -->
<!--Below Content Dependent on soapAction Selected -->
<cha:Login>
<!--Optional:-->
<cha:userName>test@oneflo</cha:userName>
<!--Optional:-->
<cha:password>efm123</cha:password>
</cha:Login>
</soapenv:Body>
</soapenv:Envelope> |
| Info |
|---|
*SoapUI automatically configures the Body Template based on the call being made. If you are using other applications you can use the "Example Body" from the required function definition below. Alternatively consult the Web Service Schema XSD (Link provided above) |
Web Service Functions/Calls
...