Writing executeBatch() XML requests for the Interact SOAP API
Use these steps to write executeBatch()
XML requests for the Unica Interact SOAP
API.
About this task
The request XML for a single operation SOAP API calls
(startSession, getOffers, setAudience, endSession
, and so on) must not be directly copied or pasted into a multiple
operation executeBatch()
call. The subcommands in
the executeBatch()
calls have slightly different
WSDL and XML request structures than those of the single operation
API calls. The structural differences cause failure responses from
the server if the XML elements are copied and pasted from single operation
API requests into multiple operation executeBatch
requests.
Sample failure responses:
** XML Response Element: <ns0:faultstring>org.apache.axis2.databinding.ADBException:
Unexpected subelement audienceID</ns0:faultstring>
** Interact Server Exception: java.lang.Exception: org.apache.axis2.databinding.
ADBException: Unexpected subelement audienceID at
*** ... com.unicacorp.interact.api.soap.service.v1.xsd.CommandImpl$Factory.parse
(CommandImpl.java:1917) at
Use these
steps to write an executeBatch()
XML request. You
can refer to single operation API call requests for parameter values
during these steps, but do not copy and paste XML elements.
Procedure
- Use a WSDL processing tool (for example, SoapUI) to create
a well-formed
executeBatch()
XML request from the Unica Interact WSDL file. - Add subcommands to the request after the WSDL definition
for
executeBatch()
child elements. - Complete the subcommand arguments after the WSDL definition
for
executeBatch()
child elements.