Data ServicessubmitJob Function for SOAP Web Services

This function submits print jobs for processing that have been specified by using LPS XML.

Tip: If you want to override the default process and job target folder used for the jobs, use submitIntegrationJob instead. For more information, see submitIntegrationJob Function for SOAP Web Services.

When you create a SOAP Web Service data service for which the WSDL URL is the Loftware Enterprise SP Services Web Services Description Language (WSDL), an operation envelope template containing this function is one of those available. For more information about using SOAP Web Services in Loftware Enterprise SP, see SOAP API for Web Services Integration.

Important! Content in a SOAP Web Service data service or a Web Service integration is case sensitive. This includes names, attributes, and values.

ClosedAbout the syntax documentation

SOAP Operation Envelope (Request)

When you create a SOAP Web Service data service, the XML of the operation envelope template that you select is displayed as the Envelope parameter. Most operation envelope templates include some elements for which you must replace the value with a value appropriate to your environment. If this operation envelope template has such elements, they are described here.

Name

Type

Description

jobFile

string

 LPS XML job data

jobType

string

 The file type, which must have a value of LXML.

SOAP Response Function

The following is the structure of the Response Function expected as part of a SOAP Response received in response to the preceding type of SOAP Operation Envelope (Request). Any ellipses indicate expected data. For more information, see SOAP API for Web Services Integration.

The response includes one result element that includes a List of Strings, where each String represents a print job ID.

<pub:SpectrumServiceResponse xmlns:pub="http://published.webservices.loftware.com/">

<return success="[true|false]">

<result xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:anyType">...
</result>

</return>

</pub:SpectrumServiceResponse>