7.6

The request can contain one or more files, one being an XMLfile containing the request information as well as any GETor
POSTvariables that were received within this request. Other files are POSTattachments.
Processing
Depending on the options chosen in the HTTPServer Input task properties, the task may choose to ignore some of the files.
For example, using the "Do not include XMLenvelope"means that only the POSTattachments will be used in the process, the
XMLfile will be discarded. Attachments are always saved on disk in a specific location, which is accessible either directly in the
XML or directly as a data file through the "Loop each attachment as data file"option.
Output
First, the output inside the process itself is, depending on the selected options, an XMLrequest files, POSTAttachments files,
either one or both.
If the "Send Immediate Response to client"option is selected, the response file is sent back right away and the involvement of
the input task ends then. However, if this option is not checked, it means there is a second output that comes out of the
HTTPServer Input task:The last output generated by PlanetPwress Watch is sent back to the initial input, which is returned
back to the client.
Starting in version 7.2 of PlanetPress Suite, you can now serve static resources through PlanetPress, which is espe-
cially useful for images, CSSand Javascript files. See HTTPServer Input 2 User Options.
HTTP Server input task properties are as follows:
l HTTP action: Enter the name of the action requested of PlanetPressSuite Workflow Tools by the client. This name
corresponds to the URLthat the client will be accessing. For example, if you enter "MakePDF" here, you could trigger
the process by accessing http://127.0.0.1:8080/MakePDF . This is also what your HTMLForm's action should be.
l MIME Type: Select the MIME type that best suits the files PlanetPressSuite Workflow Tools will be receiving as input.
l Loop each attachment as a data file: When receiving attachments through a POSTrequest (HTMLForm), this
option will make the HTTPServer Input task loop through each attachment. Each data file is an XMLwith the accom-
panied file.
l Do not include XMLenvelope:Only active when the previous Loop option is checked. When checked, the
XMLfile containing the request data will not be available. Only the attachment itself is sent as a data file.
l Respond on error: Enter a message to be sent to the client as the output file if the process encounters an error and is
unable to send a reply that includes the actual output file. The information can be in any desired format such as
HTMLor plain text, but most browsers will interpret it as plain text.
l Send immediate response to client:Do not wait for the process to finish and send a static HTMLfile back to the
client instead. This prevents any timeout from occurring. When checking this option, the field under the option is used
to select which HTMLFile to return.
"Other" Tab
l Job Information group
l Information elements:indicates what job infos 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.
l Backup input files:Check this to save a copy of each data file that is captured by your input. These files are saved in
the PlanetPress Suite Workflow Tools working folders under the "Backup"folder.
l Backup filename:Enter the filename that you wish the input data file backup to be saved under.
l Delete Existing Metadata:Check to remove any metadata from memory. This option is disabled on initial input
tasks, and is checked by default on secondary input tasks.