Xerox 6180N FreeFlow® Print Server System Guide - Page 28

JDF Workflow Example, JDF Considerations, Troubleshooting JDF

Get Xerox 6180N - Phaser Color Laser Printer PDF manuals and user guides
UPC - 095205425307
View all Xerox 6180N manuals
Add to My Manuals
Save this manual to your list of manuals

Page 28 highlights

Job submission JDF Workflow Example 1. User enables "hot folder" for the queue in the FreeFlow Print Server. 2. FreeFlow Print Server UI creates an associate Hot Folder for the queue. 3. Hot Folder Observer will create an "Error" folder in the Hot Folder if a job fails to submit to the FreeFlow Print Server. 4. FreeFlow Print Server exports the Hot Folder onto the network for job submissions. 5. User drops a data file, in a specific location in FreeFlow Print Server. The submitter drops the associated JDF job ticket into Hot Folder. 6. Hot Folder Observer sends the JDF job ticket to JDFGW. 7. JDFGW processes the ticket and sends job attributes along with data file into the FreeFlow Print Server for printing. a. When the job successfully completes printing, JDFGW writes the updated JDF ticket. b. If the JDF job ticket is invalid or JDFGW fails to submit job into the FreeFlow Print Server, JDFGW writes the updated JDF ticket to "error" sub folder". JDF Considerations • JDFGW does not support multiple input files. A JDF ticket that contains multiple input file specifications (e.g., front cover, back cover, and/or body content) must point to a single file. • A JDF ticket must have "page range" attribute specified in the input file specification. • If a JDF ticket has multiple file specifications, each specification must have "page range" set and be continuous. • Job Submission Status in the updated JDF ticket only reflects the status of successful submission into FreeFlow Print Server. • If a JDF ticket contains attributes with invalid syntaxes or invalid values, it will be moved to the "error" folder. Troubleshooting JDF The following logs are important for troubleshooting problems: If there was no response from the agent to the browser, one or all of the following can be done. 2-8 System Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
2-8
System Guide
Job submission
JDF Workflow Example
1.
User enables “hot folder” for the queue in the FreeFlow Print
Server.
2.
FreeFlow Print Server UI creates an associate Hot Folder for
the queue.
3.
Hot Folder Observer will create an “Error” folder in the Hot
Folder if a job fails to submit to the FreeFlow Print Server.
4.
FreeFlow Print Server exports the Hot Folder onto the network
for job submissions.
5.
User drops a data file, in a specific location in FreeFlow Print
Server. The submitter drops the associated JDF job ticket into
Hot Folder.
6.
Hot Folder Observer sends the JDF job ticket to JDFGW.
7.
JDFGW processes the ticket and sends job attributes along
with data file into the FreeFlow Print Server for printing.
a.
When the job successfully completes printing, JDFGW
writes the updated JDF ticket.
b.
If the JDF job ticket is invalid or JDFGW fails to submit
job into the FreeFlow Print Server, JDFGW writes the
updated JDF ticket to “error” sub folder”.
JDF Considerations
•
JDFGW does not support multiple input files. A JDF ticket that
contains multiple input file specifications (e.g., front cover,
back cover, and/or body content) must point to a single file.
•
A JDF ticket must have “page range” attribute specified in the
input file specification.
•
If a JDF ticket has multiple file specifications, each
specification must have “page range” set and be continuous.
•
Job Submission Status in the updated JDF ticket only reflects
the status of successful submission into FreeFlow Print
Server.
•
If a JDF ticket contains attributes with invalid syntaxes or
invalid values, it will be moved to the “error” folder.
Troubleshooting JDF
The following logs are important for troubleshooting problems:
If there was no response from the agent to the browser, one or all
of the following can be done.