xv
Before you proceed
Fiery X2 printing connections
The Fiery X2 supports three printing connections: Hold queue, Print queue, and
Direct connection. These printing connections can be enabled, or “published” to users
on the network, when you configure the server Setup. The Print queue and the Direct
connection give remote users more direct access to the server than the Hold queue.
Therefore, do not enable the Print queue and the Direct connection in environments
where stricter control is desired.
Hold queue
Jobs sent to the Hold queue are spooled to the server’s hard disk. These jobs cannot
proceed through the printing process without intervention via Fiery Spooler or
Fiery WebSpooler (see the
User Guide
).
N
OTE
:
The Hold queue must be published to use the Fiery utilities.
Direct connection
The Direct connection transmits jobs directly to the Fiery X2, but only when the
Fiery X2 is ready to print. If the Fiery X2 is busy, the job remains at the user
workstation until the Fiery X2 is ready. It is then processed as soon as the prior job is
finished and before the next queued job is processed.
Jobs sent to the Direct connection are not stored on the Fiery X2 hard disk and do not
appear in the display of current jobs seen from Fiery Spooler or Fiery WebSpooler;
therefore the Direct connection provides a measure of security for sensitive files. Jobs
sent to the Direct connection
do
appear in the Job Log, for accounting purposes.
N
OTE
:
The Direct connection must be used to download fonts. If you plan to
download fonts to the Fiery X2, you must publish the Direct connection.
Print queue
If you publish the Print queue, jobs sent to it are processed and printed in the order
they are received. Jobs prioritized by an operator at Fiery Spooler or Fiery WebSpooler
or jobs sent via the Direct connection can take priority over jobs sent to the Print
queue.
N
OTE
:
The Print queue must be published to use the Fiery WebTools.
