PDA

View Full Version : Using JDF NamedFeatures to reference a Fiery Virtual Printer static workflow



Mark_F
03-30-2012, 02:35 PM
If you are looking for a way to implement an automated workflow that takes advantage of a Fiery controller feature that is not covered by the JDF specification (e.g., you want to invoke automatic image enhancement to produce a photo book) or you just want a quick way to set up workflows from an application you are developing in house, without having to create full, robust JDF tickets right from the start, you may want to leverage the Fiery controller’s support for selecting a Virtual Printer using the JDF NamedFeatures attribute. 654


<JMF xmlns="http://www.CIP4.org/JDFSchema_1_2" Version="1.3" TimeStamp="2005-04-05T16:45:43+02:00" SenderID="Controller">
<Query ID="DeviceQuery" Type="KnownDevices">
<!-- DeviceDetails can have either of NamedFeature, Capability, Full values -->
<DeviceFilter DeviceDetails="NamedFeature"/>
</Query>
</JMF>

If you send a KnownDevices query with a NamedFeature, Full or Capability filter to a Fiery controller, the Fiery will respond with a list of names for the Virtual Printers currently available on that Fiery controller. Creating a JMF KnownDevices query file on disk and using the Send File feature in Alces (http://www.cip4.org/open_source/alces/) is a good way to get familiar with this functionality.

Once you have identified the NamedFeature/Virtual Printer you would like to use, just include it in the header of any JDF you send, using the format NamedFeatures="FieryVirtualPrinter MyVirtualPrinterName" where MyVirtualPrinterName is the name of your Virtual Printer. Here is an example of a very short JDF that only specifies a Virtual Printer and a PDF to print. 653


<?xml version="1.0" encoding="UTF-8"?>
<JDF Activation="Active" DescriptiveName="Polyimage" ID="ID1" JobPartID="JP1" NamedFeatures="FieryVirtualPrinter MyVirtualPrinterName" Status="Ready" Type="Combined" Types="DigitalPrinting" Version="1.3" xmlns="http://www.CIP4.org/JDFSchema_1_1" xmlns:EFI="http://www.efi.com/efijdf" xmlns:jdftyp="http://www.CIP4.org/JDFSchema_1_1_Types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AuditPool>
<Created AgentName="JDFExpress Tickets" AgentVersion="1.0.0.7" TimeStamp="2011-01-18T19:35:11+02:00"/>
</AuditPool>
<ResourceLinkPool>
<RunListLink CombinedProcessIndex="0" Usage="Input" rRef="RL1"/>
<DigitalPrintingParamsLink CombinedProcessIndex="0" Usage="Input" rRef="DP1"/>
<ComponentLink Amount="1" Usage="Output" rRef="C1"/>
</ResourceLinkPool>
<ResourcePool>
<Component Class="Quantity" ComponentType="FinalProduct"
DescriptiveName="Digital Printing Output" ID="C1" Status="Available"/>
<DigitalPrintingParams Class="Parameter" ID="DP1" Status="Available"/>
<RunList Class="Parameter" ID="RL1" Status="Available">
<LayoutElement>
<FileSpec URL="http://w3.efi.com/~/media/Files/EFI/Fiery/Fiery%20JDF/Fiery_JDF_Getting_Started_Guide.pdf"/>
</LayoutElement>
</RunList>
</ResourcePool>
</JDF>


If you add any other JDF attributes to your ticket, they will override the Virtual Printer settings. Many applications are starting to leverage this powerful functionality, including EFI solutions such as EFI Digital StoreFront web to print and EFI Pace MIS, as well as third party workflow systems like Agfa Apogee and Kodak Prinergy.