null

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

Where to find requirements?

What to Send? (Web Service WSDL)

Our Web Service Definition Language(WSDL) provides a complete overview of all calls that can be made through our SOAP Web Service, as well as the information requirements of each call.

http://support-ws.azurewebsites.net/Data/ChainIT/DataService.svc?wsdl 

Web Service Schema XSD

Within the WSDL you will also find an XSD Schema. This will inform you of the Information requirements of every call.

http://support-ws.azurewebsites.net/Data/ChainIT/DataService.svc?xsd=xsd0

This information can also be found below "Web Service Functions/Calls"

Preparing the Call

Where you are sending the information? (Endpoint)

What you are planning to do? (How to Define the Call)

i.e What function are you calling?

*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 are the information requirements

All payload/body requirements of your soap call can be found within the WSDL. This has also been documented for you on 3) Web Service Calls - Function Definition

*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)

Example Call

Logging In

In this instance I am making a call to loggin into my uat environment through postman, as I require my Session credentials to perform any further Web Service Calls.

Endpoint: https://bau-uat-ws.azurewebsites.net/Data/ChainIT/DataService.svc

Headers: 

Not Required

Header declaration is not required for SoapUI. *SoapUI does this automatically

Body:

SOAP Web Service Call Body Example
<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>

3) Web Service Calls - Function Definition

1) Preparing your Machine for SOAP Integration

  • No labels