JDF job tickets

When you submit a job using a JDF job ticket, the hot folder input device reads the job ticket and uses the contents to find the print files and to set properties for the job. The job is created after all the print files have been found.

The figure Hot folder input device processing with JDF job tickets shows how hot folder input devices process jobs that are submitted with JDF job tickets. The input device accepts job files, processes them based on their batching methods, and sends them to the SubmitInputFiles step.

Hot folder input device processing with JDF job tickets

This image shows how hot folder input devices process jobs that are submitted with JDF job tickets. The input device accepts job files including job tickets, which it treats as overrides files, and processes them as described in the text.

In this section:

  1. Setting job properties from the JDF job ticket
    RICOH ProcessDirector can use the values that it supports in the JDF job ticket to set job properties.
  2. Viewing the JDF job ticket
    Some values in the JDF job ticket are not shown in the RICOH ProcessDirector user interface, but the workflow might call an application that uses these values. Therefore, you might need to view the JDF job ticket.
  3. Locating files
    Applications that submit jobs with JDF job tickets can either send the files along with the job ticket, or leave the files in another location on the network. The job ticket is not required to list the files that the job contains. However, if the job ticket does list the files, it can use either relative path names or absolute path names.
  4. Using a mapping file to find input files
    If you use a Job Definition Format (JDF) job ticket to submit jobs to a Hot folder device, you do not have to copy all the input files to the Hot folder. When the job ticket is placed in the Hot folder, RICOH ProcessDirector reads it and searches for the input files that it lists.
Parent topic: Files for batch jobs