7.1

l After you have created this queue, on every remote computer that will be sending data files to PlanetPress Suite Work-
flow Tools you will need to create a printer queue connecting to the PlanetPress Suite Workflow Tools queue.
To ensure that the spooled files created by the PlanetPress Suite Workflow Tools queue remain in the spool folder, PlanetPress
Suite Workflow Tools requires that the queue be paused.
Note that when you add or edit a WinQueue input task, if you select a printer queue that is not currently paused, a message
will be displayed prompting to pause the printer. Also note that if the selected queue uses enhanced metafile spooling, a mes-
sage box will be displayed prompting you to disable this option (PlanetPress Suite Workflow Tools does not support this fea-
ture which provides minimal benefits for PostScript printing).
WinQueue input task property is as follows:
General tab
l Printer queue: Select the PlanetPress Suite Workflow Tools printer queue (the one to which data files are going to be
sent).
l Printer properties group
l Advanced printing features: Select to create EMF files for Windows Print Converter action tasks (see "Win-
dows Print Converter Action Task Properties" (page 115)). Note that this option must not be selected when cap-
turing generic text type data.
l Paused: Select to pause the selected printer queue.
l Spool file pooling: Select to turn on spool file pooling for the selected printer queue. Note that selecting this
feature may cause problems, so only use it if you know exactly what you are doing.
HTTP Server Input Task Properties
HTTP Server input tasks are used to receive HTTP requests made via GET or POST commands and to send replies to the
servers from which the requests were made. The HTTP server supports both http and https.
While you can insert the HTTPServer Input Task anywhere in your process as a secondary input task, in reality the
HTTPServer Input Task will only function when used as the initial input, as it is triggered when the PlanetPress Suite
Workflow Tools HTTPServer receives a request and passes it on to the correct task.
HTTP Server input tasks are typically used in one of the two following situations:
l HTML Form Action: An HTMLForm in the browser that may contain text and attached files can be filled and sent to a
process with the HTTPServer Input Task.
l HTTP Data Submission: A custom application or a server sends the request to PlanetPressSuite Workflow Tools using
either a POST or GET command. The application or server then waits for a response from PlanetPressSuite Workflow
Tools.
When the HTTPServer Input Task receives a request through either situation, it receives all the text and input fields, converts
them into an XMLformat, saves any files submitted, and passes this data to the following task. When the process completes
(when the last output has been generated), whatever was generated is returned to the client via the HTTPServer itself.
This is important for multiple reasons:
l In most cases, you would want to either return a file understandable by the client (like a PDF or a ZIPfile), or an
HTMLfile that a browser can display. This is accomplished by making sure the last action task is generating that file (be
it the Digital Action task, a Create File where you type in the HTMLor a Load External File that gets an existing
HTMLfile), and the actual output task is a Delete Output Task. Even if the job file is "deleted", it is first returned to the
application or client that made the request.
©2010 Objectif Lune Inc - 101 -