PDA

View Full Version : JDF tickets that reference content files on Windows shares



Mark_F
03-13-2012, 05:58 AM
Supporting JDF job tickets that reference content files on Windows shares is possible, but configuring a Fiery controller to retrieve files on a Windows share is more complex and requires a workaround for System 9r2 Fiery controllers and for System 10 Fiery controllers either a common global path configuration or manual intervention on each job.

System 9r2 Fiery controllers with the Fiery JDF feature set v1.0
Many customers use Fiery controllers without logging in to Windows on the Fiery controller itself. In order for the Fiery controller to start up its services and become available on the network before anyone logs in, most of the Fiery controller's services log in as the local system account, rather than a local user (Administrator or another one added to the Fiery controller itself) or a domain user (e.g., domain\username).

While this makes the Fiery controller available on the network as soon as possible, JDF workflows that access files on Windows shares require a workaround. Microsoft Windows allows only actual user accounts (not the local system account) to access Windows shares on a network (e.g., \\server_name\share_name\path\file_name.pdf)

To enable a system 9r2 Fiery controller with the Fiery JDF feature set v1.0 to access files on Windows shares, set the Fiery CSI Atom service to log in as Administrator:Fiery.1 or the user that will log in to Windows on the Fiery controller:

Launch the Services control panel Start\Control Panel\Administrative Tools\Services (or Start\Run\services.msc)
Select the Fiery CSI Atom service, and right click to access properties (screen shot of Services control panel)
On the Log On tab of the Fiery CSI Atom Properties dialog, specify This account: using whatever account is used to log into Windows on the Fiery controller (the shipping default on Fiery controllers is Administrator:Fiery.1).
Restart the Fiery CSI Atom service.

Note that the Fiery JDF (Fiery CSI Atom) service will not start up until that specific user logs in. If a different user logs in, it will not start up at all. You may want to configure the Fiery controller to automatically log in to Windows with Administrator:Fiery.1 or whatever account is specified in the Fiery CSI Atom service properties Log On attribute.

System 10 Fiery controllers with the Fiery JDF feature set 1.1
The Fiery JDF feature set 1.1 that ships with System 10 Fiery controllers adds two mechanisms that make it easier to support JDF job tickets that reference content files on Windows shares.

Whereas System 9r2 Fiery controllers will reject the job if it cannot retrieve content since the JDF content RunList is read-only, the run list can be edited in the JDF settings dialog on System 10 Fiery controllers, allowing CWS operators to manually resolve content RunList issues.

System 10 also provides access to defining a common global path for JDF workflows, saving user name and password login credentials to network shares for a file search path. This feature has long been popular for VDP workflows, but System 10 makes it available for JDF workflows as well. Configuring a common global path to shares integrated workflows use for content files enables the Fiery controller to automatically retrieve content files referenced on Windows shares.