JDF Server
 |
Administrator access level only!
If you select the Apogee System in the Hardware pane, you will see the JDF Server icon in the Resources pane.
By double-clicking the JDF Server icon, you can access the JDF Server settings. These allow you to specify how Apogee builds the production plan for jobs submitted by the JDFServer or JDF Import, and how Apogee communicates with external systems used to input JDF files.
NOTE: JDF is a licensed feature.
JDF Server Settings
The JDF Server dialog box comprises four tabs which allow you to specify how Apogee builds the production plan for jobs submitted by the JDFServer or JDF Import, and how Apogee communicates with external systems used to input JDF files.
Administrator access level only!
Job Settings
Milestones
When a milestone is present in the JDF, Apogee sets the appropriate ‘milestone’ time in the job’s Options tab, and sets the notification to be sent some time before the specified milestone occurs.
Notify before
Specify the notification time.
Product Definition
You have the option to match the JDF job with a Product whose name matches the value of @ProductTypeDetails or select a preferred preset for the different assembly types. Choose a preset Product from the drop-down lists for the different assembly types. If you clear both check boxes, the Default Product you choose in this drop-down list is used.
Apogee Impose
Choose a Press Sheet Layout rule from this drop-down list for JDF jobs.
Sheet Prefixes
Choose whether you want to use sheet prefixes of Production Sets in multi-part jobs or not at all.
Content
By default, Apogee attempts to retrieve every content element as specified by the JDF, even in cases where none of them are located in their intended locations. When there are numerous missing documents for a job, this could take a while. In such a case, you can select the check box Stop retrieving content files as soon as one goes missing.
PlateMaker Link
You can enable the synchronization of separations between Prepress and PlateMaker servers by selecting the check box. As soon as rendered separations become available, they are transferred from Prepress Server to PlateMaker Server.
Planless Submission
This tab defines how Apogee builds the production plan for jobs submitted by the JDFServer or JDF Import. Apogee uses these settings as defaults when it receives a ‘planless’ job description or an incomplete plan, such as submitted by a Hot Ticket with only a JDF Input.
Production Plan: Build dynamically
Apogee will check the incoming JDF/JMF for processes/grayboxes, and will use this information to dynamically create the production plan for jobs.
Output device
Select a high-resolution output device from the list. If high-resolution output is requested in the JDF but no specific device is specified, then this high-resolution output device will be used.
Imposition proofer
Select any proofer other than the TIFF Proofer. If proofing is requested in the JDF but no specific proofer is specified, then this proofer will be used.
Proofer data by
Select how the page proofer receives its data:
•Separate Render: Apogee splits the imposition proof flow into two flows before the main Renderer, and uses a separate Renderer to drive the proofer.
•Digital Film Proof: Apogee splits the imposition proof flow into two flows after the main Renderer, and inserts a Digital Film Proofer to drive the proofer.
Page Proofer
Select a proofing device for page proofing from a list of all available proofers.
Press
Select a press from the list of available presses. If you select a Generic Press, you can also select a Press Parameter Set.
Digital Press
Select a Digital Press from the list of available Digital Presses.
Sign and Display Printer
Select an S&D printer from the list of available S&D Printers.
JMF Input
Choose a JDF Import parameter set that contains the prepress expansion from the drop-down list.
Action Points
Select the actions you need in the job’s Production Plan. By default, no actions are added, except ‘Collect for Output’ before the main device. Note that the ‘Collect for Output’ action before the main device is set to collect by Job, and the one before the proofing device is set to collect by Page. None of the actions are set to Notify. The ‘Collect for Output’ action before the proofer flow is set to hold the results; you cannot select to continue them automatically.
•Add ‘Soft Proof’ before Impose Main Flow
•Add ‘Soft Proof’ before each Render TP
•Add ‘Hard Copy Proof’ before Render Main Flow
•Add ‘Keep Results’ on Render Main Flow
•Add ‘Collect for Output’ before Main Device
•Automatically start printing
•Add ‘Collect for Output’ before Proofing Device
Put job on hold
If this check box is selected, the (not-intent) job stays on hold at the input channel until you continue it.
Put intent job on hold
If this check box is selected, the intent job stays on hold at the input channel until you continue it.
Production Plan: Use Ticket Template
Apogee will use a ticket template to create the job. You can select a hot ticket template for regular jobs or for so-called layout jobs. See “Working with Hot Tickets” and “Wide Format Hot Tickets”.
Hot Ticket Template
From Category
Lists all categories and all Ticket Templates for Hot Tickets.
Default Template
specify a Default Template to be used for the various JDF job types.
Templates for Job Types
The five different job types correspond to a combination of specific grayboxes present in the submitted JDF. The fifth ‘job type’ is for assigning a ticket template to Intent jobs:
•Main flow only
•with Page Proofing
•with Imposition Proofing
•with Page and Imposition Proofing
•Intent jobs
•Digital Print jobs
Layout Hot Ticket Template
From Category
Lists all categories and all Ticket Templates for Layout Hot Tickets.
Default Template
specify a Template to be used for the various JDF Layout job types.
Product Integration
These options allow you to specify how Apogee communicates with external systems and applications, such as an MIS system.
JDF Attribute Mapping
The structure of a JDF job depends largely on the MIS vendor and the way a site uses it. To support the different structures, Apogee can map its attributes to the different parts in the JDF. This is especially important for administrative attributes. The mapping between JDF and Apogee attributes is stored in a JDF Attribute Map resource.
Base Attribute Map
Defines the common attribute mappings used by most vendors.
Edit Maps
opens the JDF Attribute Maps overview window. You can add, duplicate, edit and delete JDF Attribute Maps using the corresponding buttons. You can also import and export maps.
Mis URL
Only required for integration with StoreFront. Enter the URL where the MIS expects to receive JMF messages.
Apogee WebApproval
Use Collaborators from MIS or WebApproval
This option specifies that Apogee should honor the list of collaborators as listed in the JDF job or ignore that list and use the list of collaborators set up in the WebApproval application.
Apogee Webserver
Port
The port number of the Apogee Web server. Note that this does not set the port number. Apogee simply needs this number to pass on to external systems that need to connect to the web server. The default port number is 80.
Input
Pre-process
“This option allows you to pre-process every file found in the Hot Folder before it is handled by the JDF Input Task Processor. Pre-processing input files is mainly used to ‘fix’ JDF files, and helps to integrate JDF products from different vendors.
Run script on incoming JMF
Specify the full path to the script you wish to execute. At runtime, the script is started with two or more arguments.
Optional arguments
Enter optional runtime arguments. Separate multiple arguments with spaces. If you need to specify an argument with a space in it, you must enclose that argument in single or double quotes, or you need to replace the space with a backslash. You can use Apogee variables as arguments. The JMF Input Task Processor substitutes each variable before passing it to the script. To avoid problems with spaces, JMF Input encloses each substituted string in double quotes.
Run script on incoming JDF
Specify the full path to the script you wish to execute. At runtime, the script is started with two or more arguments.
Optional arguments
Enter optional runtime arguments. Separate multiple arguments with spaces. If you need to specify an argument with a space in it, you must enclose that argument in single or double quotes, or you need to replace the space with a backslash. You can use Apogee variables as arguments. The JDF Input Task Processor substitutes each variable before passing it to the script. To avoid problems with spaces, JDF Input encloses each substituted string in double quotes.
Remove content files on external servers
This option determines whether or not Apogee removes externally referenced content files, and is deselected by default. This option only applies to files located in a Public Page Store or on a disk that is not being watched by a Hot Folder. It does not apply to files located on a WebServer or in a Hot Folder, Files in a Hot Folder are always removed when they are moved into a job: Files referenced by other methods are never removed.
Extract thumbnails from PDF
JDF Server can extract the thumbnails of a PDF for viewing in the Results tab (when available). This option is available for all JDF jobs, regardless of how they were input (i.e. JDF Import or via JMF). This reduces the processing load, since the Normalizer does not have to create the thumbnails (which is slower than simply extracting them).
Output
Include all partitions in resource messages
By default, all redundant information is removed from resource messages. Select the check box to include this information.
Post-process
Run script on output JMF
Applies a post-processing script on outgoing messages towards MIS or Press. This can be used as a workaround to adapt messages if MIS has issues with it.
Optional arguments
Enter optional runtime arguments. Separate multiple arguments with spaces. If you need to specify an argument with a space in it, you must enclose that argument in single or double quotes, or you need to replace the space with a backslash. You can use Apogee variables as arguments. The JMF Input Task Processor substitutes each variable before passing it to the script. To avoid problems with spaces, JMF Input encloses each substituted string in double quotes.
Run script on output JDF
Applies a post-processing script on outgoing JDF. This can be used as a workaround to adapt a JDF if the receiver has issues with it.
Optional arguments
Enter optional runtime arguments. Separate multiple arguments with spaces. If you need to specify an argument with a space in it, you must enclose that argument in single or double quotes, or you need to replace the space with a backslash. You can use Apogee variables as arguments. The JDF Input Task Processor substitutes each variable before passing it to the script. To avoid problems with spaces, JDF Input encloses each substituted string in double quotes.
NOTE: Note that digital presses have their own script configuration
Output Accounting
Report when output is made
Enables JMF reporting of the results that are produced.
Edit Cost Types
Click this button to tailor the reporting to your requirements. This displays the Cost Types dialog box where you can create, edit or delete a number of cost types. These allow you to track the number of plates that are being made, both for keeping the stock inventory up to date and to perform post-calculations
•Reason Text: A textual short description of the reason for the remake. This is what the operator will see.
•Cost Type: Whether the remake has to be charged to the customer or not.
•Work Type: Why the plate is being remade:
•Original: First output of a plate (included in the order).
•Alteration: Remake because content has changed.
•Rework: Remake of the original plate (no changes in content, processing). For example, if the plate was scratched.
Job Finishing Events
This section deals with the information that is exchanged between Apogee and the MIS system when a job nears its end of life. It specifies when Apogee should archive and delete a job, and when Apogee should report that a job is finished.
NOTE: You must respect the logical order of the events and actions.
Report ‘ReturnQueueEntry’ when:
Determines when Apogee sends the ReturnQueueEntry (RQE) event, signaling to the MIS that it has completed the job.
•Apogee finishes the job: Send RQE when the job finishes (i.e. when the finished marks appear in front of the job).
•Apogee archives the job: Send RQE when Apogee has archived the job - but only when the job is finished. Note that this does place any restrictions on the event that triggers the archiving process.
•Apogee deletes the job: Send RQE when Apogee has deleted the job. Note that this does place any restrictions on the event that triggers the deletion process.
•MIS sends PrePress Completed: Send RQE when the MIS sends a PrePressCompleted event.
•MIS sends Press Completed: Send RQE when MIS sends a PressCompleted event.
•MIS sends PostPress Completed: Send RQE when the MIS sends a PostPressCompleted event.
•MIS sends Shipping Completed: Send RQE when the MIS sends a ShippingCompleted event.
•MIS sends Job Completed Successfully: Send RQE when the MIS sends a JobCompletedSuccessfully event.
Archive when:
Select when to start the archival process:
•Honor job’s ‘Finish’ options: Apogee archives the job according to the respective options set in the job’s Option tab.
•When MIS sends <...> Completed: Apogee archives the job upon receiving a specified milestone event: PrePressCompleted, PressCompleted, PostPressCompleted, ShippingCompleted, JobCompletedSuccessfully.
Delete when:
Select when to start the deletion process:
•Honor job’s ‘Finish’ options: Apogee deletes the job according to the respective options set in the job’s Option tab.
•When MIS sends <...> Completed: Apogee deletes the job upon receiving a specified Milestone event: PrePressCompleted, PressCompleted, PostPressCompleted, ShippingCompleted, JobCompletedSuccessfully.
JDF Updating
A number of options control when a JDF job update is granted or denied. These options include unnotified acceptance or denial, or notified update.
There are a number of conditions that allow different update policies according to the current stage of the job.
As long as Run List is empty
The Run List is currently empty. Default is Allow.
As soon as Run List contains a page
There is at least one page placed, but no output has been made. Default is Allow.
A result, other than main has been output
The job has produced at least one proof (or any other output other than from the main flow). Default is Notify.
A main result has been output
The job has produced at least one result from a main flow. Default is Deny and inform
When job was edited
The job was edited by the operator. This is not an actual phase of the job; it is a state that the job can be in, regardless of which stage it is in. Default is Allow.
Apogee determines the stage of a job by inspecting it when receiving a JDF update; it does not maintain a history. Internal result states are cleared when a result (or job) is reprocessed, or when a page leading to a result is removed from the Run List.
The available policies for each of these stages are as follows:
•Allow: Allows the MIS to apply JDF job updates without asking, and without informing the operator that there was an update.
•Apply and Inform: Applies all JDF job updates without asking, but posts a notification after applying the updates.
•Notify: Posts a notification when a JDF job update needs to be applied. The operator can then decide whether to accept or deny the update.
This policy should only be used when the MIS supports asynchronous JMF commands. Otherwise, the MIS will fail the update when the operator does not immediately answer the notification.
Apogee returns an error to the MIS upon receiving a synchronous command, and posts a notification. The notification states that the update was rejected because of a misconfiguration, and suggests you either change the MIS protocol settings or use a different update policy. The same message is included in the error reply sent to the MIS.
•Deny: Denies the JDF job update without asking, and without informing the operator that the update was denied.
•Deny and Inform: Denies the JDF job update without asking, but posts a notification informing the operator that the update was denied.
Cogwheel menu
Compare Configuration
Compares the JDF Server settings against the default values.
Restore Defaults
Restores all settings to their factory defaults.
doc. version 13.1.1