2021.1

The Input SOAP Task only responds to a single SOAP action by the client: SubmitJob. Within
this request however, a secondary action (SubmitSOAPActionName) can be specified - this is
what the SOAP Action corresponds to in this task properties.
Input
This task does not poll any location by itself. It sits there waiting for requests coming in through
WSDL (SOAP communication) and, when it receives a request, runs the process and returns
the last output generated by the process to the client.
Processing
No processing is done. The request that is received by this task is XML and it is maintained as
such.
Output
As with the HTTP Server Input, this task has a dual-output purpose. First, when the initial input
task is run, the XML request is output onto the process. Then, when the process is finished, the
last job file generated by the process is returned to the requesting client.
Task properties
General Tab
l
SOAP Action: The SOAP action is used with the SubmitJob action. It’s the equivalent of
the process name. The difference is that more than one processes can share the same
SOAP action. That way more than 1 CPU can be used to process all the incoming
requests however this means that all process sharing the same SOAP action must be
identical because there is no way to decide the execution order of all the process.
"Other" Tab
l
Job Information group
l
Information elements: Indicates what Job Info variables are automatically created
by the input task.
l
Add lines before first data page: Using the arrows keys you can add any job
information directly at the beginning of your data file.
Page 338