Creating WSDL for Unitary Interactions




We're trying to call Campaign inbound offers from a Sitecore page. To do this, I need to generate a WSDL file. I'm following the process outlined in Web service calls , using the schemas identified in Integration via SOAP (server side) . I am getting an XML response, but it seems not to be a proper WSDL file to me.



If I try another schema, I get a "full" WSDL returned:


Could anyone please tell me what the "right" schemas are for inbound offers, or better still, where I could find a list of the available schemas ?

Thanks and regards,


Answers (4)

Answers (4)




Hi Neil,

There is no official WSDL for it. I'll give you the basic SOAP call structure which you can make use of or enhance it as per requirement.











       <context><interaction ranking='1' /></context>  



You can make use of it to generate a WSDL for your use case




Thanks @shrawanas31530030.

Here's what I get back for http://XXXXXXXXXX/nl/jsp/schemawsdl.jsp?schema=nms:interaction :

<?xml version="1.0" encoding="UTF-8" ?>

<definitions targetNamespace="urn:nms:interaction" xmlns="" xmlns:s="" xmlns:soap="" xmlns:tns="urn:nms:interaction" xmlns:wsdl="">

- <types>

  <s:schema elementFormDefault="qualified" targetNamespace="urn:nms:interaction">

  <s:complexType name="Element">


<s:any processContents="lax" />





<portType name="interactionMethodsSoap" />

- <binding name="interactionMethodsSoap" type="tns:interactionMethodsSoap">

<soap:binding style="document" transport="" />


- <service name="NmsInteraction">

  <port binding="tns:interactionMethodsSoap" name="interactionMethodsSoap">

<soap:address location="http://XXXXXXXXXX/nl/jsp/soaprouter.jsp" />




This does not seem to be a complete & valid WSDL file to me, compared to what I get back if I pass xtk:session as the schema name.

I saw someone respond in another thread that no WSDL available to call the Interaction engine, but this to me suggests that either the documentation is wrong, or the Interaction service does not properly implement SOAP.

I know there are code workarounds for not having WSDL, but to me a lack of WSDL support is not acceptable for an enterprise platform.

Thanks for any advice.