Incorrect WSDL results in objects not showing in web service soap client connector operation import wizard

Document created by mike_aronson Employee on Feb 11, 2016Last modified by ruchika_yadav on Mar 1, 2016
Version 2Show Document
  • View in full screen mode
When using the import wizard in a web service soap client connector operation, the objects do not show up.  There could be several reasons for this. 
One reason for this could be that the WSDL for the web service was not defined correctly.

 

The Web services SOAP Client Connector supports SOAP 1.1 and 1.2, but works best with web services that adhere to the WS-I Basic Profile 1.1 specification as described at this link:

http://help.boomi.com/atomsphere/GUID-DD65922D-746F-4DAE-B9C5-45A05A477D53.html

 

When this scenario is observed, sometimes the web services may get generated in soapUI but not in Boomi.

 

In one case that we came across, we observed that WSDL did not define any services. There should be a service element defined after the bindings element:

 

Here is an example for where the NetSuite WSDL defines a service element after the bindings element:

 

</binding>
<service name="NetSuiteService">
<port name="NetSuitePort" binding="tns:NetSuiteBinding">
<soap:address location="https://webservices.na1.netsuite.com/services/NetSuitePort_2015_1"/>
</port>
</service>
</definitions>

 

After the WSDL was modified to include a similar service element section, then the object was able to be imported correctly.  This is just one example where the WSDL
was not complete and therefore was not able to be imported into Boomi.  There may be other reasons for an incomplete WSDL as well.  The WSDL should be inspected for
compliance if issues like this one are observed.
1 person found this helpful

Attachments

    Outcomes