Konica Minolta Digital StoreFront - Manual (Page 144)

Digital StoreFront 5.2 Administration Reference
144
jobs to another print shop for production. This capability allows your business to process orders
efficiently and continue operations if one print shop cannot function due to power outage,
equipment failure, etc. Specifying one or more print shops as output devices will make them
available for selection on the Operator View page. This will enable operators to assign a job that is
routed to one print shop to be printed at a different print shop. This allows load balancing
between print shops or moving a job to another print shop that has the capabilities required to
produce the job. You will be prompted to choose a destination print shop from the Choose
Destination Print Shop.
4. In the Display Name field, type a descriptive name for the output device.
5. In the Output Ticket XML field, select which type of job ticket to generate for the output device:
• Digital StoreFront (default ticket for all non-JDF output devices, including MicroPress)
•
JDF (for folder-based output devices such as CD-Rom and Folder; this option defaults to
“process” ticket and NT Shared path URL)
•
MIME Package:
o
mjm: the content file will contain JDF instructions and the JMF message.
o
mjd: the content file will contain JDF instructions.
Consult with your output device vendor to determine which method should be
used with their device.
• Ticket Type:
Consult the chart below in section Notes on JMF JDF Structure for Job Submission
for guidance on when to use process and intent for various output devices.
o
Process (default): Specifies actual information defining how the job is to be produced.
Use for Fiery outputs; contains Fiery-specific instructions.
o
Intent: Preserves print buyer’s intent for the file (buyer-entered web-form data
suggests, for example, that she intends to receive a 5,000 copies of a 100-page spiral
bound book on 8.5x11 white paper, with a glossy 100lb. four-color cover, full color,
etc.). Use for non-Fiery JDF outputs.
Process and Intent are the two main types of instructions gathered into a JDF job
ticket.
•
FileSpec URL: URL of the JDF content file. Specifies how the job ticket gets delivered.
o
MIMEEncoded: Content file will be MIME encoded along with JMF and JDF and sent
through the connector to the output device.
o
HTTP: JMF message will have a link to the JDF file as a shared path URL and the JDF file
will have a link to the content file as a shared path/HTTP/HTTPS URL.
o
NTShared (Network Shared): Job ticket XML is embedded in the content file sent
through the connector to the output device.
6. In the Device Directory field, type a valid directory path. It is recommended that you create this file
directory as a subfolder in the installation folder for the system.