Creating WSDL for Unitary Interactions

Avatar

Avatar

neild75794353

Avatar

neild75794353

neild75794353

20-06-2018

Hi,

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.

http://XXXXXXXXXX/nl/jsp/schemawsdl.jsp?schema=nms:proposition

http://XXXXXXXXXX/nl/jsp/schemawsdl.jsp?schema=nms:interaction

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

http://XXXXXXXXXX/nl/jsp/schemawsdl.jsp?schema=xtk:session

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,

Neil

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

pablo_rosero1

Avatar

pablo_rosero1

pablo_rosero1

29-11-2018

Hi Neil,

Here's how to Capture Adobe Campaign SOAP traffic with Fiddler​ and then load it to WASL with an Action activity​.

I hope this helps!

All the best,

Pablo

Answers (4)

Answers (4)

Avatar

Avatar

neild75794353

Avatar

neild75794353

neild75794353

21-06-2018

Thanks Vipul.

The WSDL is missing the complexType definition for the ProposeResponse.

ProposeResponse_WSDL.jpg

Are you able to provide a sample please?

Thanks,

Neil

Avatar

Avatar

Vapsy

Employee

Avatar

Vapsy

Employee

Vapsy
Employee

21-06-2018

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.

<urn:Propose>

    <urn:sessiontoken></urn:sessiontoken>

    <urn:targetId>1643624892</urn:targetId>

    <urn:maxCount>20</urn:maxCount>

    <urn:uuid></urn:uuid>

    <urn:nlid></urn:nlid>

    <urn:noProp></urn:noProp>

    <urn:categories></urn:categories>

    <urn:themes></urn:themes>

    <urn:context>

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

    </urn:context>

</urn:Propose>

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

Regards,
Vipul

Avatar

Avatar

neild75794353

Avatar

neild75794353

neild75794353

21-06-2018

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="http://schemas.xmlsoap.org/wsdl/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="urn:nms:interaction" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

- <types>

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

  <s:complexType name="Element">

  <s:sequence>

<s:any processContents="lax" />

</s:sequence>

</s:complexType>

</s:schema>

</types>

<portType name="interactionMethodsSoap" />

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

<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />

</binding>

- <service name="NmsInteraction">

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

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

</port>

</service>

</definitions>

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.

Avatar

Avatar

shrawans3153003

Employee

Avatar

shrawans3153003

Employee

shrawans3153003
Employee

20-06-2018

Hi Neil,

Schema name's seems correct.