Professional Documents
Culture Documents
Workflow System
Version 5.0
731-00463C-EN Rev J
Copyright
© 2008 Kodak. All rights reserved.
This document is also distributed in Adobe Systems Incorporated's PDF (Portable Document Format). You may reproduce
the document from the PDF file for internal use. Copies produced from the PDF file must be reproduced in whole.
Trademarks
Kodak, Creo, Business Link, Connect, Direct, DotShop, Evo, EyeMedia, InSite, Pandora, Powerpack, Preps, Prinergy, Publish,
PDF Compare, PDF Merge, PDF Trapper, Trap Viewer, Trap Editor, Advanced Trap Editor, Separation Viewer, Geometry
Editor, Separation Repair, View Accelerator, Kodak Distiller Assistant, and Color TIFF XT are trademarks of Kodak.
Adobe, Acrobat, Adobe Illustrator, Distiller, Photoshop, and PostScript are trademarks of Adobe Systems Incorporated.
Apple, AppleShare, AppleTalk, iMac, ImageWriter, LaserWriter, Mac OS, Power Macintosh, and TrueType are registered
trademarks of Apple Computer, Inc. Macintosh is a trademark of Apple Computer, Inc., registered in the U.S.A. and other
countries.
PANTONE, Hexachrome, PANTONE Hexachrome, and PANTONE MATCHING SYSTEM are the property of Pantone, Inc.
FCC compliance
Any Kodak equipment referred to in this document complies with the requirements in part 15 of the FCC Rules for a Class
A digital device. Operation of the Kodak equipment in a residential area may cause unacceptable interference to radio and
TV reception, requiring the operator to take whatever steps are necessary to correct the interference.
Equipment recycling
In the European Union, this symbol indicates that when the last user wishes to discard this product, it
must be sent to appropriate facilities for recovery and recycling. Contact your local Kodak representative
or refer to http://www.kodak.com/go/recycle/ for additional information on the collection and recovery
programs available for this product.
Limitation of liability
The product, software or services are being provided on an “as is” and “as available” basis. Except as may be stated specifically
in your contract, Kodak expressly disclaims all warranties of any kind, whether express or implied, including, but not limited
to, any implied warranties of merchantability, fitness for a particular purpose and non-infringement.
You understand and agree that, except as may be stated specifically in your contract, Kodak shall not be liable for any direct,
indirect, incidental, special, consequential or exemplary damages, including but not limited to, damages for loss of profits,
goodwill, use, data or other intangible losses (even if Kodak has been advised of the possibility of such damages), resulting
from: (i) the use or the inability to use the product or software; (ii) the cost of procurement of substitute goods and services
resulting from any products, goods, data, software, information or services purchased; (iii) unauthorized access to or
alteration of your products, software or data; (iv) statements or conduct of any third party; (v) any other matter relating to
the product, software, or services.
The text and drawings herein are for illustration and reference only. The specifications on which they are based are subject
to change. Kodak may, at any time and without notice, make changes to this document. Kodak assumes no liability for
technical or editorial errors or omissions made herein, and shall not be liable for incidental, consequential, indirect, or special
damages, including, without limitation, loss of use, loss or alteration of data, delays, or lost profits or savings arising from
the use of this document.
http://graphics.kodak.com/
2 System overview 3
What is Prinergy?..........................................................................................................................................................................3
Software components...................................................................................................................................................................3
Architecture....................................................................................................................................................................................6
Servers..............................................................................................................................................................................................7
Job components.............................................................................................................................................................................8
Distributing the system................................................................................................................................................................9
Web browser access...................................................................................................................................................................10
Installation folder (%AraxiHome%) .......................................................................................................................................11
3 Licenses 13
Licensing.........................................................................................................................................................................................13
Prinergy options............................................................................................................................................................................15
Viewing licensed options...........................................................................................................................................................19
Selecting a core dongle for Prinergy........................................................................................................................................19
Entering a license key.................................................................................................................................................................20
Manually enabling a license key..............................................................................................................................................20
Saving license key information.................................................................................................................................................21
Removing a license key..............................................................................................................................................................22
Replacing a dongle......................................................................................................................................................................22
Removing a license key......................................................................................................................................................23
Inserting a dongle..............................................................................................................................................................23
Entering a license key........................................................................................................................................................23
Selecting a core dongle for Prinergy..............................................................................................................................24
4 JTPs 25
JTPs.................................................................................................................................................................................................25
Types of JTPs................................................................................................................................................................................26
Monitoring JTPs...........................................................................................................................................................................28
Starting or stopping a JTP.........................................................................................................................................................29
Adding JTPs..................................................................................................................................................................................30
Removing a JTP............................................................................................................................................................................34
JTP distribution guidelines........................................................................................................................................................34
Pooling JTPs..................................................................................................................................................................................36
JTP pools..............................................................................................................................................................................36
Creating a JTP pool............................................................................................................................................................37
Changing an existing JTP pool........................................................................................................................................38
Types of JTP pools..............................................................................................................................................................39
vi Prinergy
5 Users 41
User accounts............................................................................................................................................................................41
Configuring users in a domain..............................................................................................................................................42
Configuring users in a workgroup........................................................................................................................................43
Setting user rights....................................................................................................................................................................44
6 Servers 47
Prinergy servers........................................................................................................................................................................47
Setting up a secondary server...............................................................................................................................................49
Creating an Araxi service account on a Windows server....................................................................................49
Creating a job or input volume on a Windows server............................................................................................50
Adding a secondary server to the system..................................................................................................................51
Adding a server to the HOSTS file of the other servers........................................................................................52
Setting up a tertiary server.....................................................................................................................................................52
Qualified tertiary servers and Mac client computer file-sharing protocols......................................................52
Setting up a Windows tertiary server........................................................................................................................55
Setting up a Windows Server 2003 cluster tertiary server..................................................................................62
Setting up a Brisque tertiary server............................................................................................................................79
Creating an Araxi service account on a UNIX server............................................................................................79
Setting up Samba on a Brisque 4 or Brisque Serve server....................................................................................79
Setting up Samba and setting up volumes on a Brisque 5 server......................................................................80
Creating an input volume on a Brisque server........................................................................................................80
Creating a job volume on a Brisque server..............................................................................................................80
Adding a server to the HOSTS file of the other servers..........................................................................................81
Identifying non-SFM servers in the OTHERHOSTS file..........................................................................................81
Adding a tertiary server or input volume to the system........................................................................................83
Testing a tertiary server................................................................................................................................................84
Setting up an Xserve tertiary server..........................................................................................................................84
Setting up a generic UNIX tertiary server..................................................................................................................92
Creating an Araxi service account on a UNIX server............................................................................................92
Installing connectivity software on a generic UNIX server..................................................................................93
Configuring a UNIX share with SMB..........................................................................................................................93
Creating a job or input volume on a UNIX server ..................................................................................................94
Adding a server to the HOSTS file of the other servers........................................................................................95
Identifying non-SFM servers in the OTHERHOSTS file..........................................................................................95
Adding a tertiary server or input volume to the system........................................................................................97
Testing a tertiary server................................................................................................................................................98
Monitoring servers...................................................................................................................................................................99
Changing server configurations..........................................................................................................................................100
Selecting a network card on the primary server....................................................................................................100
Removing an input volume..........................................................................................................................................100
Removing a server..........................................................................................................................................................101
Updating the OTHERHOSTS file to change a non-Windows server..................................................................101
Changing the password of the Araxi service in a domain..................................................................................102
Changing the name of the Araxi service account..................................................................................................103
File resources....................................................................................................................................................................112
Storing file resources......................................................................................................................................................113
Archiving and Mac client computer file-sharing protocols..................................................................................114
Setting up Mac client computer file-sharing protocols.................................................................................................114
Starting SFM to support AFP......................................................................................................................................114
Configuring AFP with ExtremeZ-IP............................................................................................................................115
Identifying non-SFM servers in the OTHERHOSTS file........................................................................................119
Updating the SFMHOSTS file......................................................................................................................................121
Enabling Preps under SMB............................................................................................................................................121
Changing Mac client computer file-sharing protocols..................................................................................................123
Limitations of protocol conversions using Prinergy Administrator..................................................................123
Converting to SMB with AppleDouble....................................................................................................................124
Converting to AFP..........................................................................................................................................................128
Manually converting protocols....................................................................................................................................131
Converting files with Fork Translator........................................................................................................................133
Troubleshooting..............................................................................................................................................................134
12 Preferences 155
RIPs.............................................................................................................................................................................................155
Selecting the default RIP for new jobs...............................................................................................................................156
Signature ID codes .................................................................................................................................................................156
Configuring the default signature ID code.......................................................................................................................158
Non-essential history entries..............................................................................................................................................160
Controlling how long history logs are kept........................................................................................................................161
viii Prinergy
Job folders.................................................................................................................................................................................162
Defining custom job folders.................................................................................................................................................163
Configuring the behavior of hot folders............................................................................................................................164
Controlling the error messages that Prinergy displays.................................................................................................165
Configuring thumbnail compression and resolution.....................................................................................................166
Setting approval requirements............................................................................................................................................166
Displaying all IS screens in Process Template Editor.....................................................................................................167
Controlling revisioned pages for InSite..............................................................................................................................167
Administering Dashboard....................................................................................................................................................169
13 Monitoring 171
Daemons ...................................................................................................................................................................................171
Viewing processes..................................................................................................................................................................174
Identifying Process IDs..........................................................................................................................................................175
15 Archiving 187
What Archiver does...............................................................................................................................................................187
Components of the Archiver system.................................................................................................................................188
Setting up the Archiver.........................................................................................................................................................189
Archiving to disk.....................................................................................................................................................................190
About archiving to disk................................................................................................................................................190
Adding archive disk volumes......................................................................................................................................190
Modifying archive disk volumes..................................................................................................................................191
Removing archive disk volumes..................................................................................................................................192
Archiving to tape.....................................................................................................................................................................193
Setting up removable storage devices......................................................................................................................193
Archiving job data to tape..........................................................................................................................................194
Supported tapes and devices......................................................................................................................................195
Tape labels......................................................................................................................................................................196
Archive tape storage strategies..................................................................................................................................198
Removable Storage Manager......................................................................................................................................199
16 Backup 203
What backup does.................................................................................................................................................................203
Components of the backup system..................................................................................................................................204
Backups with third-party software....................................................................................................................................204
Backup planning............................................................................................................................................................204
Configuring backups with third-party software....................................................................................................207
Performing a backup with third-party software....................................................................................................208
Prinergy Online Backup option...........................................................................................................................................209
Prinergy Online Backup..............................................................................................................................................209
Allocating tapes for backup........................................................................................................................................210
Contents ix
17 Maintenance 217
Performing daily maintenance tasks..................................................................................................................................217
Performing weekly maintenance tasks..............................................................................................................................217
Performing monthly maintenance tasks...........................................................................................................................218
Freeing disk space...................................................................................................................................................................218
Compressing the database..................................................................................................................................................220
Disk clean-up tool...................................................................................................................................................................221
20 Glossary 231
x Prinergy
1 Getting started
Basic information that you need when you install Prinergy® for the first
time.
See also:
Licenses on page 13
JTPs on page 25
Users on page 41
Servers on page 47
Proofing devices on page 137
Adding output devices on page 145
RBA setup on page 149
Preferences on page 155
Starting Prinergy
Use Prinergy Administrator to start the Prinergy Server software on one
or more servers.
Note: Prinergy must be running on the primary server before you can
start Prinergy on a secondary server.
3. Click Start.
Prinergy may take a moment to start up. You can watch the processes start in
the Processes pane.
See also:
Viewing processes on page 174
Stopping Prinergy
Use Prinergy Administrator to stop the Prinergy Server software on one
or more servers.
3. (Optional) In the Reason for Shutdown box, type the reason for
stopping Prinergy.
This information is logged in the Windows® operating system event
log to assist with troubleshooting.
4. Click Stop Prinergy.
Prinergy may take a moment to shut down. You can watch the processes shut
down in the Processes pane.
See also:
Viewing processes on page 174
2 System overview
What is Prinergy?
The Kodak Prinergy workflow system is a PDF-based, printing
workflow–management tool that organizes prepress and plate production.
The Prinergy system manages tasks such as file optimization, trapping,
color management, proofing, color matching, imposition, archiving,
film-making, and plate-making for increased process control and
productivity.
Prinergy is a scalable system, allowing you to use only the components
that you need for your workflow. You can easily add functionality by
enabling features.
Software components
Prinergy is a client/server system that includes the Workshop client
software and several server software components.
Workshop is installed on all client computers, the primary server, and each
secondary server.
Even if your Prinergy system includes only one server, you should have at least
one client computer to run Workshop.
Workshop software is primarily written in the Sun™ Java™ language, a
platform-independent language that enables Workshop to run and look the same
on both Mac OS® and Windows operating systems. Java software runs on top
of a Java Virtual Machine (VM) that provides the interface between application
software and the operating system. The VM for Mac OS is Apple® Macintosh®
Runtime for Java (MRJ), and the VM for Windows is Java Runtime Environment
(JRE).
Server Software
The server software side of a Prinergy system is called Prinergy Server. It includes
several components, which can be installed on multiple servers.
These components are installed on all primary and secondary servers.
Software Purpose
Prinergy Administrator Acts as the user interface for Prinergy Server software. It
(UADM.exe ) is where you control Prinergy Server software and the
Prinergy system.
JTPs (multiple) Process PDF files and their contents—for example, trapping
Software Purpose
®
Oracle software Stores job information, including file attributes, history
(Oracle.exe) and information, and pointers to input files—but doesn’t store
database file content
Oracle Backup Backs up the system drive and database to tape or disk.
Manager
Software Purpose
® ®
Adobe Reader View PDF files, which are the internal file type of the
Prinergy system
®
AppleTalk Font Download and install fonts
Downloader
®
Harmony Calibrate dot gain
Prinergy DotShop Edit a Screen Instance File (SIF) to define the screen
Composer instances supported by your system and used by Prinergy
DotShop
™
Symantec Access the Prinergy system remotely
pcAnywhere
Some Prinergy servers also have companion software, such as Kodak Print
Console or Kodak InSite™.
Important: Never install unauthorized software on your Prinergy system.
Architecture
Prinergy uses PDF as the internal file format, tracks tasks with job tickets,
and distributes tasks to job ticket processors.
Job tickets
A job ticket is a collection of information relating to one task. It always includes
an outline of processing steps that need to be performed. It may also include
other information, such as the files to process, destinations, and so on.
Job tickets enable Prinergy to perform processing in the background without the
need for user interaction.
Job tickets use the Portable Job Ticket Format (PJTF), a control mechanism for
specifying the sequence of operations and parameters that are to be performed
on PDF files. PJTF is part of Adobe Extreme® technology, a high-end,
production-printing architecture.
A job ticket takes its name from the Extreme technology practice of equating a
job with a task. Except for the term job ticket, Prinergy documentation uses the
standard prepress definition for a job—a related collection of customer files—not
a task.
Servers 7
CORBA communication
Prinergy uses Common Object Request Broker Architecture (CORBA®) for some
internal communications. CORBA allows software to communicate with one
another, no matter where they are located or who designed them.
The Object Request Broker (ORB) is the middleware that brokers the
communication between client and server software—for example, between
Prinergy Workshop and the various Prinergy daemon processes on the server.
Prinergy uses an implementation of CORBA by IONA® Technology PLC called
Orbacus® and OrbacusWeb. It uses TCP/IP as the core networking protocol.
Not all communication in Prinergy relies on CORBA. Adobe Extreme does not
use CORBA and has its own communication structure. However, Extreme still
uses TCP/IP as the underlying protocol.
Servers
A Prinergy system includes one primary server and any number of
secondary, tertiary, or file servers.
The following table describes each type of Prinergy server and identifies
the software installed on it, the operating system requirements, and
whether it stores jobs.
8 Chapter 2—System overview
Primary server Coordinates requests from All server software, Windows 2000 Server Yes
Workshop and maintains the including the database or Windows 2003
database Server
Secondary Runs some or all JTPs to Administrator Windows 2000 Server Yes
servers distribute processing or Windows 2003
One or more JTPs
Server
For example, an archiving station
Some daemons
runs archiving JTPs
Tertiary servers Stores jobs. Does not perform None Windows is Yes
processing. recommended
File servers Stores input files, does not None Any server that you No
perform processing, and is not can access
called a Prinergy server
Job components
In Prinergy, a job is the unit used to organize work. A job typically
corresponds with all the components related to a single publication. Every
job has a “home server,” which is the server where it is stored.
A Prinergy job has the following components:
Distributing the system 9
A job folder Contains the files for a job, including In the Jobs folder on the job’s home server
named after the the system files that Prinergy generates,
job such as master PDF files and
thumbnails
Database Information about a job, including the: An Oracle database on the primary server
information
● Location of all files
● Status of job elements
● History information
Note: Never modify job system files (in the System subfolder in the job
folder). If you do, Prinergy may not be able to reference job components.
For more information about job folders, see Prinergy Workshop Help.
Documentation
Documentation URL and port
Note: Depending on your site's needs, only one type of Workshop Help—Connect
or Powerpack—may be available. The help systems are configured when Prinergy
is installed.
Installation folder (%AraxiHome%) 11
Software components
Use URL Port
%AraxiHome%
When you see %AraxiHome% in a file path, it refers to the installation folder of
Prinergy software.
%AraxiHome% is an environment variable in the Windows operating system.
It is set during the Prinergy installation.
Installation folder
The installation folders for Prinergy software are listed in the following table:
Ensure that the system contains the licenses required to run the features
and JTPs that you want.
Licensing
Use licensing to customize and expand your Prinergy system to suit your
needs. By entering an appropriate license key, you can enable additional
features and add more JTPs.
Core license
Important: Always use the primary Prinergy server to work with licensing. Do
not work with licensing on a non-primary server, such as a secondary or tertiary
server.
A single license key is used to license permanent features on your system. It
appears in the Dongle Security Code box of the License Information dialog box.
If you buy additional permanent features, you are assigned a new license key that
includes all the permanent features for which you are licensed.
You may be able to select unlicensed options when adding a JTP or creating a
process template. However, only the licensed options will run successfully when
you use the process template.
Dongle
A dongle is a security device that plugs into a port on the computer (usually the
parallel or USB port) to allow licensed features to work. If a dongle is damaged
or lost, contact your service representative to request a new dongle.
If other Kodak software, such as Kodak InSite, is installed on the same server,
license it using the same dongle, so that one dongle is shared across products. If
the other Kodak software is installed on a different server, you need a dongle for
that server.
feature may be listed in the License Information dialog box. These features are
enabled on a JTP-by-JTP basis.
After you enter all licenses, save a copy of the license information and keep it in
a safe place. If a license is accidentally removed or if the dongle is damaged, you
will need this information.
Screen licensing
Most screen systems require licenses. In general, you need a separate license
for each screen that you use in Prinergy.
Some screens have different types of licensing. For information about each type
of screen licensing, see the following table:
Type Description Screens of This Type How It Is Enforced
Screen name Every screen has its own Most screens, including You cannot selected unlicensed screens in
licensing license. all screens with names a process template in Workshop.
that start with ID
Prinergy options 15
™
Maxtone Maxtone screening has its Maxtone screening If you type a value greater than 1 in the
screen own licensed Highlights box or Shadows box in the
licensing MaxTone area in the Calibration and
Screening section of an output process
template, and Maxtone screening is not
licensed, the process fails.
After you enter a license key for a screen, enable it in each output JTP using the
the JTP Properties dialog box. High-resolution output JTPs use different screen
systems from low-resolution JTPs. Some output JTPs do not use any screening,
including Copydot, PostScript Level 3, and Vector Output.
For more information about screens, see Workshop Help.
Prinergy options
Extend your Prinergy system with features whose benefits range from
improved output quality to increased system reliability. For purchasing
information, contact your Kodak sales representative.
Advanced Provides advanced profile-based preflighting to identify
Preflighting and correct problems in the input files. Includes a profile
editor so that users can create their own profiles.
Generates a preflight report that itemizes the results,
with links to the objects in the PDF Digital Master.
Archiver Archives files to store them on tape, purges files to free
disk space, and retrieves files from a tape to restore a
job.
Business Link
Provides the ability to bi-directionally connect Prinergy
with qualified MIS systems using JDF®. The production
reports that are included in the software also allow
users to run several pre-configured reports from a
web-based interface, independent of an MIS.
The exchange of product and process related JDF job
data with qualified MIS systems allows the complete
automation job creation & set up in Prinergy. Imposition
information from an MIS can be automatically imported
16 Chapter 3—Licenses
1. On the primary Prinergy server, from the License menu, select Manage
License Key.
2. In the Dongle Security Code box, view the identification code for the
dongle that is attached to your system.
3. In the License Keys box, select the license key that you want to view
information about.
4. View the information about that license, including:
Item Identifies
Option column The name of the option—for example, the JTP name
Expiry Date The date the option expires—for example, you may be using
column some options on a trial basis
5. Repeat steps 3 and 4 for each item in the License Keys box.
1. On the primary server, from the License menu, select Manage License
Key.
2. Click Change.
The Choose Dongle Security Code dialog box displays a list of all valid
dongles on the server, including dongles for Prinergy and InSite.
3. Select a dongle, and click OK twice.
Next:
If you are finished working with licenses, start Prinergy on all servers in
the system.
20 Chapter 3—Licenses
1. On the primary Prinergy server, from the License menu, select Manage
License Key.
2. Click the Enter License Key button.
3. Perform one of the following actions:
● If you know your new license key, copy and paste the license key
in the New License Key box.
● To read a license key from a file, enter a file name in the Load Key
From File box (type the name, or click Browse to find the file), and
click Read File.
4. Click Apply.
5. Click OK.
6. If you are finished working with licenses, start Prinergy on all servers
in the system.
Next:
With some licensed features, you must manually enable the license before
the feature can be used, even though the feature may be listed in the
Prinergy Licensed Information dialog box.
After you enter all licenses, save a copy of the license information and
keep it in a safe place. If a license is accidentally removed or if the dongle
is damaged, you will need this information.
2. With the JTP selected, from the Prinergy Administrator main menu,
select JTP.
3. From the submenu, select Properties.
4. In the JTP Properties dialog box, select the features for which you
purchased a license.
5. Click OK.
6. Stop the JTP and start the JTP the JTP in order for the feature to take
effect.
Next:
After you enter all licenses, save a copy of the license information and
keep it in a safe place. If a license is accidentally removed or if the dongle
is damaged, you will need this information.
1. On the primary Prinergy server, from the License menu, select Manage
License Key.
2. In the License Keys box, select a license key.
3. Click Save to File.
4. Select a location to save the file to, and type a file name.
5. Click Save to save a snapshot of all your licensed options to a .key
file.
6. Click OK.
22 Chapter 3—Licenses
7. If you are finished working with licenses, start Prinergy on all servers
in the system.
1. On the primary Prinergy server, from the License menu, select Manage
License Key.
2. In the License Keys box, select the license key that you want to remove.
3. Click Remove License Key.
4. Click Remove.
5. Click Yes to confirm you want to remove the license key.
Important: Removing a license key disables all associated features.
6. Click OK.
7. If you are finished working with licenses, start Prinergy on all servers
in the system.
Replacing a dongle
If a dongle is damaged or lost, or if you want to change from a parallel
dongle to a USB dongle, contact your service representative to request a
new dongle.
1. Removing a license key
2. Inserting a dongle
3. Entering a license key
4. Selecting a core dongle for Prinergy
Requirements:
Contact your service representative to request a new dongle. When you
receive the dongle, ensure you have the dongle's license key that is usually
sent by e-mail.
Removing a license key 23
1. On the primary Prinergy server, from the License menu, select Manage
License Key.
2. In the License Keys box, select the license key that you want to remove.
3. Click Remove License Key.
4. Click Remove.
5. Click Yes to confirm you want to remove the license key.
Important: Removing a license key disables all associated features.
6. Click OK.
7. If you are finished working with licenses, start Prinergy on all servers
in the system.
Inserting a dongle
Insert a dongle into a port on the Prinergy server.
1. On the primary Prinergy server, from the License menu, select Manage
License Key.
2. Click the Enter License Key button.
24 Chapter 3—Licenses
4. Click Apply.
5. Click OK.
6. If you are finished working with licenses, start Prinergy on all servers
in the system.
Next:
With some licensed features, you must manually enable the license before
the feature can be used, even though the feature may be listed in the
Prinergy Licensed Information dialog box.
After you enter all licenses, save a copy of the license information and
keep it in a safe place. If a license is accidentally removed or if the dongle
is damaged, you will need this information.
1. On the primary server, from the License menu, select Manage License
Key.
2. Click Change.
The Choose Dongle Security Code dialog box displays a list of all valid
dongles on the server, including dongles for Prinergy and InSite.
3. Select a dongle, and click OK twice.
Next:
If you are finished working with licenses, start Prinergy on all servers in
the system.
4 JTPs
Monitor JTPs to determine their status, stop and start JTPs if they are not
responding, and add and remove JTPs when rebalancing the resource load
in your system.
JTPs
A JTP is software that performs a specific step to help process a job ticket.
There is a JTP for each kind of processing step that can be performed in
the Prinergy system. Each JTP has a unique name.
Monitoring JTPs
You can check the status of JTPs and identify which server(s) they are on.
Adding JTPs
All JTPs are installed on Prinergy servers. However, the Prinergy system cannot
use a JTP until the JTP has been activated. You activate a JTP by "adding it" to a
server in Administrator. You can deactivate a JTP by stopping the JTP or by
"removing it" from a server in Administrator.
When you add a JTP to a server, you must give the JTP a unique, descriptive
name. Exceptions to this rule are the archiving and Import/Export JTPs, which
can't be renamed.
The JTPs that you add in Administrator appear in Workshop in the process
templates. In general, each section of a process template requires a JTP.
26 Chapter 4—JTPs
JTP distribution
To facilitate load sharing and to optimize performance, your system may use:
● Multiple instances of a JTP type (on the same server or on different
servers)--to enable simultaneous processing of multiple jobs
● Different JTPs on different servers--to balance resource loads
● Pooled JTPs--to automatically distribute job tickets to servers in the pool
(Used when you have more than one instance of a JTP type.)
Important: Your Prinergy configuration and JTP distribution were carefully
considered by your service representative. You should not need to redistribute
your JTPs. Contact your service representative before redistributing or adding
multiple instances of existing JTPs.
The number and type of JTPs that you can distribute depends on your licensing
agreement.
See also:
Types of JTPs on page 26
Types of JTPs
Each JTP in Prinergy performs a specific function, which is indicated by
its icon and group.
Icon JTP Type Description Group
Color Matcher Generates data for color-matching proofs to final output Refine
Refine and
Copydot Optimizes copydot files for output
Output
Disk Purge Removes selected jobs or files from the job server Archive
Types of JTPs 27
Heidelberg
Sends data to a Heidelberg Herkules output device Output
Herkules®
Heidelberg
Sends data to a Heidelberg Primesetter output device Output
Primesetter®
Heidelberg
Sends data to a Heidelberg Quasar output device Output
Quasar®
Heidelberg
Sends data to a Heidelberg Signasetter output device Output
Signasetter
Optimizes PDF files into digital masters that are suitable for
Optimize print and checks conditions such as compression and Refine
downsampling
PrintLink Generates PPF (CIP3) files for digital ink key preset systems Output
28 Chapter 4—JTPs
Proofing Device Create high-resolution (512 MB) output that is suitable for
Output
(512 MB) proofing
Speedway Engine
Sends data to a Heidelberg SpeedWay® output device Output
Manager
Topsetter® Engine
Sends data to a Heidelberg Topsetter output device Output
Manager
Monitoring JTPs
View information such as the name of the JTP, server where the JTP
resides, type of JTP or JTP pool, status of the JTP, and so on.
● In the right pane, click the JTPs tab.
The JTP window displays the following information:
Column Describes
JTP
Name User-defined name or generic name for the JTP or JTP pool
Column Describes
Status ● Ready: It has been added to the server and is ready to use.
● Stopped (offline): It has been added to the server but is
temporarily disabled.
See also:
Types of JTPs on page 26
JTP pools on page 36
3. The Status column of the JTPs tab displays either Stopped (offline)
or Ready.
30 Chapter 4—JTPs
Adding JTPs
Add a JTP to perform a specific type of processing on a specific server in
your Prinergy system.
1. From the JTP menu, select Add JTP and then select one of the
following types:
● Archive
● CopyJob
● Generate
● Import/Export
● Output
● Refine
Adding JTPs 31
2. For archive, output, and refine JTPs, select a specific JTP in the JTP
Type box:
For this
Select one of these JTPs
type
● Archive/Retrieve
Archive
● Disk Purge
● CEPSConversion
● Color Matcher
● Copydot
Refine
● Normalize
● Optimize
● Trap
Note: Some JTPs, such as Printlink, Marks, and CTM Transform, can
be added only once. If they already exist, they no longer appear in the
JTP Type box.
32 Chapter 4—JTPs
4. In the Host Server list, select a server to add the JTP to.
Note: For an Archive JTP, select the server that is connected to the
archiving device.
Adding JTPs 33
5. For certain JTPs, next to Features, select the check boxes for specific
features:
For this type of
Select
JTP
● Staccato 20 Series
● Staccato 10 Series
● Staccato 25 Series
DOP, Expose,
Heidelberg ● MaxTone Screening
devices, Print ● Seamless Screening
Console,
Proofing devices, ● DigiCap
and Topsetter ● Hyperflex Basic
● Hyperflex Advanced
● Kodak IS Screening
34 Chapter 4—JTPs
● VectorOutput:DSC 2
VectorOutput ● VectorOutput: Separated PS
● VectorOutput: PDF
See also:
Types of JTPs on page 26
Removing a JTP
Remove a JTP from a server when you no longer need the JTP.
they are not CPU-intensive, they are disk-intensive and could saturate the local
disk.
A good JTP setup for an 8-CPU server consists of:
● 2 Normalizers
● 2 Optimizers
● 2 Color Managers
● 1 Trap
● 1 Import/Export
● 3 Proof JTPs
● Perhaps 1 or 2 extra refine JTPs as required.
Pooling JTPs
Group JTPs into pools to automatically distribute tasks to individual JTPs.
JTP pools
A JTP pool is a collection of two or more JTPs of the same type that have
been grouped together to further automate your workflow.
A JTP pool enables you to direct Prinergy to automatically distribute tasks
to individual JTPs when they become available. Without pools, the JTP
that you select in a process template must be a specific JTP on specific
server.
Unless you have specific reasons for doing otherwise, it is recommended
that you pool JTPs of each type, and that you select the pools in your
process templates.
Note: Final Output JTPs cannot be pooled.
1. From the JTP menu, select Create JTP Pool, and then select a pool
type.
Type Description
Optimize Optimizes PDF files into digital masters that are suitable
for print and checks conditions such as compression and
downsampling
38 Chapter 4—JTPs
Type Description
1. On the JTPs tab, select the name of the JTP pool to which you want
to add a JTP.
Types of JTP pools 39
Add a JTP to From the JTP menu, select Properties. In the Selected JTPs
the pool in the pool box, select the check box beside each JTP that you
want to add.
Remove a JTP From the JTP menu, select Properties. In the Selected JTPs
from the pool in the pool box, select the check box beside each JTP that you
want to remove.
Remove the From the JTP menu, select Remove JTP pool.
pool completely
CEPSConversion Converts Brisque CT/LW and TIFF/IT P1 pages to composite PDF 1.3 output
Generates a layered PDF 1.5 file from a group of refined PDF 1.3 files. Used
Generate
by the Prinergy Layered PDF Versioning system.
Exports all or part of a job to a compressed file for import into another
Prinergy system. Also imports imposition plans, populated job tickets
Import/Export
(imposition plans with job pages already assigned to page positions), and
compressed files exported from Page Assigner.
Optimizes PDF files into digital masters that are suitable for print and checks
Optimize
conditions such as compression and downsampling
PostScript Level 3 Enables Prinergy to output jobs and files in the PostScript 3 file format
Proofing Device (256MB) Creates low-resolution output that is suitable for proofing
Proofing Device (512MB) Creates high-resolution output that is suitable for proofing
Outputs loose pages to the continuous tone/line work (CT/LW) format for
CT/LW processing and printing in the Brisque workflow system and other workflow
systems
Set up accounts for each user, assign them to groups, and give them rights
to advanced tasks in Workshop.
User accounts
User accounts have several advantages, can be organized into groups,
and should have strong passwords.
About passwords
Passwords are case-sensitive. They must be a maximum of 14 characters. If a
user plans to access the Workshop software from an Apple Mac® computer, the
user's password must be a maximum of 8 characters, because Mac computers
can accept passwords of up to 8 characters only.
To help safeguard your system, encourage "strong" passwords for all accounts
used with Prinergy. Strong passwords:
● Contain characters from all four of these classes: uppercase characters,
lowercase characters, numerals, and non-alphanumeric special characters,
such as punctuation and symbols
● Are not obviously associated with the user. For example, they do not contain
any part of the user's identification, such as the name used for e-mail, the
name of the user account, the user's real name, and so on.
42 Chapter 5—Users
c. Select the User must change password at next logon check box,
and click OK.
Configuring users in a workgroup 43
c. Select the User must change password at next logon check box,
and click OK.
44 Chapter 5—Users
Create, modify, and delete custom fields for jobs and job elements.
Manage Without this right, the Custom Fields Manager dialog box appears
Custom in read-only mode. The user cannot create, modify, or delete custom
Fields fields. This permission does not affect a user's ability to enter values
into custom fields.
5. Click OK.
The user rights take effect the next time that the user logs on to the Prinergy
system.
46 Chapter 5—Users
6 Servers
Prinergy servers
A Prinergy system can include different types of servers, which can store
jobs and input files.
Types of servers
The Prinergy system can include several types of servers.
● The primary server is the main server in a Prinergy system. There is only one
primary server in a Prinergy system. It contains all Prinergy Server software
components, including the Oracle database. The primary server coordinates
requests from the Prinergy Workshop software and maintains the database.
● Secondary servers are servers that run the Prinergy Server software but are
not the primary server and do not have the Oracle database. You can
potentially add any number of secondary servers to your Prinergy system.
● Tertiary servers are file servers. They are part of the Prinergy system but are
not running the Prinergy Server software. Tertiary servers can store jobs and
input files.
1. Log on as an administrator.
2. If the Araxi service account is set up on the domain controller, you
can skip this step; otherwise create the Araxi service account:
a. From the Start menu, select Programs > Administrative Tools >
Computer Management.
b. On the Tree tab, click Local Users and Groups to expand the tree.
c. Right-click Users, and select New User. You can use the default
user name of ARAXI.
d. Follow the prompts.
Give the new account the user name and password that your site
uses for the Araxi service account. The default user name is ARAXI.
Clear the User must change password at next logon check box
and select the Password never expires check box.
f. Click Add or Add User or Group. From the Name box, select the
Araxi service account, click Add, and click OK.
The Local Security Policy Setting dialog box appears, and the Araxi
service account appears in the Assigned To box.
g. Click OK.
4. Add the Araxi service account to the Administrators group.
1. On the server that you want to add to Prinergy, create the folder that
you will share.
Ensure that the folder is:
● On an NTFS volume, or an error will occur when you share the
folder
● At the root level, not within another folder
type a name in the Macintosh share name box using the correct
format.
For a job volume, use the format Jobs on <server letter>
<drive letter> Drive, such as Jobs on Server1 G
Drive.
For an input volume, you can use any format.
You can also use ExtremeZ-IP™ to enable AFP connections from
Mac client computers without Services for Macintosh (SFM).
h. Click Next, click Finish, and click No to indicate that you do not
want to create another share.
3. Give permissions to the folder in one of the following ways:
● Give everyone full control.
● Deny read/write access. Instead, create user accounts for the users
who need to modify PDF files or add customer files, and give the
user accounts read/write access to the folder.
For information about using the operating system to set folder
permissions, see the operating system documentation.
Tertiary server Mac client computer protocol Service level and comments
Windows Server 2000 and Windows Either of the following protocols: ● Service level 1, if the server is
Server 2003 purchased from Kodak
● AFP with SFM
● Service level 3, if the server is
● AFP with ExtremeZ-IP
not purchased from Kodak
We are working to qualify this operating
system for SMB with ADS, if all Mac client
computers run Mac OS X 10.5. Do not use
SMB with ADS until it is qualified.
Mac OS X Server 10.4 SMB with AppleDouble Service level 2 until Mac OS X
Server 10.5 is qualified.
Service level 3 after Mac OS X
Server 10.5 is qualified.
Mac OS X Server 10.5 Qualified for AFP for Prinergy 4.1.2.2 and Service level 2, when this solution
higher. is qualified
Not yet qualified for any other protocol
54 Chapter 6—Servers
Tertiary server Mac client computer protocol Service level and comments
Brisque Server, which uses Samba AFP via Helios Service level 1
and Helios
Archiving is not supported.
UNIX with Samba and an AFP server, AFP via the AFP server Service level 3
®
such as Helios or Xinet
Archiving is not supported.
UNIX with Samba and no AFP server SMB with AppleDouble Service level 3
Service level 3 The solution is documented but not tested with every major
upgrade and not supported. Support is limited to
documentation.
A problem will be investigated only if it meets the following
conditions:
● The problem is caused by Prinergy.
● The problem can be replicated on a job volume on the
customer's Prinergy primary server. The customer must
keep the job volume on the primary server for this purpose.
After a Prinergy upgrade, you must confirm that the solution
still works to your satisfaction. Consider buying a software
testing solution to test upgrades before implementing them
on a production system. For information about testing
solutions, contact your sales representative.
Setting up a Windows tertiary server 55
1. Log on as an administrator.
2. If the Araxi service account is set up on the domain controller, you
can skip this step; otherwise create the Araxi service account:
a. From the Start menu, select Programs > Administrative Tools >
Computer Management.
b. On the Tree tab, click Local Users and Groups to expand the tree.
c. Right-click Users, and select New User. You can use the default
user name of ARAXI.
d. Follow the prompts.
Give the new account the user name and password that your site
uses for the Araxi service account. The default user name is ARAXI.
Clear the User must change password at next logon check box
and select the Password never expires check box.
f. Click Add or Add User or Group. From the Name box, select the
Araxi service account, click Add, and click OK.
The Local Security Policy Setting dialog box appears, and the Araxi
service account appears in the Assigned To box.
g. Click OK.
4. Add the Araxi service account to the Administrators group.
1. On the server that you want to add to Prinergy, create the folder that
you will share.
Ensure that the folder is:
● On an NTFS volume, or an error will occur when you share the
folder
● At the root level, not within another folder
type a name in the Macintosh share name box using the correct
format.
For a job volume, use the format Jobs on <server letter>
<drive letter> Drive, such as Jobs on Server1 G
Drive.
For an input volume, you can use any format.
You can also use ExtremeZ-IP to enable AFP connections from
Mac client computers without Services for Macintosh (SFM).
h. Click Next, click Finish, and click No to indicate that you do not
want to create another share.
3. Give permissions to the folder in one of the following ways:
● Give everyone full control.
● Deny read/write access. Instead, create user accounts for the users
who need to modify PDF files or add customer files, and give the
user accounts read/write access to the folder.
For information about using the operating system to set folder
permissions, see the operating system documentation.
● Perform this task to identify all non-SFM servers (that is, servers not
using Microsoft Services for Macintosh) in your system with any Mac
client computer protocols—not only with AFP.
● This task applies whenever you configure Mac client computer
protocols.
● Prinergy performance suffers unless you ensure that all non-SFM
servers are listed in the OTHERHOSTS file. Otherwise, Prinergy makes
RPC calls to the SFM service on the server. These calls occur
frequently—for example, every time a page is refined. Although the
calls eventually time out, they affect Prinergy performance.
1. Locate %AraxiHome%\etc\otherhosts.
2. Open the otherhosts file in a text editor.
3. Locate the [/etc/otherhosts] section, and add
"*:MyServerName"="MyServerName" as the third line.
[/etc/otherhosts]
"SOMEZONE:blatserver1"="NTBLATSERVER1"
"SOMEZONE:blatserver2"="NTBLATSERVER2"
"*:MyServerName"="MyServerName"
Example
In this example:
● The tertiary server is called "TertiaryServer" and it is
configured in the Mac Zone "Prinergy Lab".
● The first volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Mac computers.
● The second volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Windows 2000-based computers.
● The Mac share name is "Jobs on TertiaryServer".
● The Samba share name is "AraxiVolume_TertiaryServer".
[/etc/otherhosts]
"Prinergy
Lab:TertiaryServer"="TertiaryServer"
[shares]
NtHost="TertiaryServer"
"Jobs on
TertiaryServer"="AraxiVolume_TertiaryServer"
"AraxiPreps"="AraxiPreps"
See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128
Requirements:
It is the customer's responsibility to set up, configure, and maintain
Windows Server 2003 cluster tertiary servers. Kodak does not provide
any assistance with the actual cluster beyond what is contained in this
document.
Meeting requirements to use a Windows cluster 63
2. Set up drive Q:
a. Ensure that only the first node is turned on.
b. Right-click My Computer and select Manage > Storage.
c. Double-click Disk Management.
d. If the Write Signature and Upgrade Disk Wizard appears, select
Write Signature but do not upgrade the disk to dynamic. Click
Next.
e. Right-click Unallocated disk space.
f. Select New Partition.
g. The New Partition Wizard starts. Click Next.
h. Select Primary partition type. Click Next.
i. The default is set to maximum size for the partition size. Click Next.
(Multiple logical disks are recommended over multiple partitions
on one disk.)
j. Use the list to change the drive letter. Use drive letter Q for the
quorum disk.
k. Format the partition using NTFS. Label the volume as Drive Q.
Labeling the volume can be helpful during troubleshooting.
2. Configure a network name for the cluster group that will be configured
in Prinergy as the tertiary server name.
a. Right-click the Group where the resource will belong. Select New
> Resource.
b. Type the resource Name and Description. In the Resource type
list, select Network Name. Click Next.
c. Add both nodes as possible owners of the resource. Click Next.
d. On the Dependencies page, add the IP address resource that you
created in the previous section. Click Next.
e. Type a unique NetBIOS name for the network name resource. The
name can be up to 15 characters long. Click Finish.
A dialog box should appear with the message that the resource
was created successfully.
f. Bring the resource online by right-clicking it, and selecting Bring
online.
3. Add a file share resource:
a. Add new resource using Resource type > File Share.
b. Type the resource Name and Description. Click Next.
c. Add both nodes as possible owners of the resource. Click Next.
d. On the Dependencies page, add the shared physical disk resource
that will host this share. Click Next.
e. Type the Share name (typically, AraxiVolume), Path, and
Comment. Click Permissions to modify permissions to allow full
access to the Araxi service logon account. You may also need to
modify permissions for other users. Click Finish.
A dialog box should appear with the message that the resource
was created successfully.
f. Bring the resource online by right-clicking it, and selecting Bring
online.
d. Click Stop.
e. In the Startup type list, select Disabled and click OK.
f. In the right pane, right-click Print Server for Macintosh and select
Properties.
g. Click Stop.
h. In the Startup type list, select Disabled and click OK.
When SFM stops, all AFP shares are deleted, so there is no need
to manually remove AFP mappings.
If you do not disable the service, a message about migrating SFM
shares appears when you start ExtremeZ-IP for the first time. You can
either click Yes to migrate all shares, or click No and create the shares
manually for SMB and Mac shares.
2. Install the ExtremeZ-IP File Server software on the Prinergy server
using the ExtremeZ-IP Quick Start Guide that is available at
http://www.grouplogic.com.
3. If you just installed ExtremeZ-IP, you can start the ExtremeZ-IP
Administrator immediately. Otherwise click Start > Programs >
ExtremeZ-IP > ExtremeZ-IP Administrator.
If a warning appears that non-standard port 549 is in use, you can
ignore this warning for now as you will change it later.
4. When you see the message The server contains Services for
Macintosh (SFM) shares. Would you like to migrate these
shares to ExtremeZ-IP volumes nad disable SFM?, perform either
of the following actions:
● If you are installing on a primary or secondary server, click Yes to
migrate all shares.
● If you are installing on a tertiary server, click No because you will
create the shares manually for SMB and Mac shares.
b. Click the Security tab, and confirm that the following check boxes
are cleared.
● Allow Workstations to Save Password
● Show Only Accessible Volumes
● Reset Permission on Moves (Global)
● Notify Mac Clients of Password Expirator
● Enable IPv6
c. Click the Search tab, and confirm that the Use lazy indexing check
box is cleared.
d. Click the Filename Policy tab, and confirm that all of the check
boxes are cleared.
e. Click the Service Discovery tab, and confirm that the Zidget/HTTP
check box is cleared.
Important: The Server Name must not have IP at the end of the
server name. Otherwise the server will appear twice in the Finder.
f. Click OK.
7. If you are installing on a primary or secondary server, and you migrated
shares, follow the left column to modify the path of the volume.
If you are installing on a tertiary server, and you did not migrate shares,
follow the right column to create an ExtremeZ-IP share for Prinergy.
When creating shares, ensure you follow these conventions:
● The Windows Share Name must start with AraxiVolume_ and must
use the same folder path as the ExtremeZ-IP share.
● The AFP and ExtremeZ-IP Volume Name cannot exceed 27
characters.
● If you have existing jobs and are adopting ExtremeZ-IP, do not
change share names.
Setting up a tertiary server 75
In the Volumes dialog box, select the Jobs In the Volumes dialog box, click
on J drive volume, for example, Jobs on Create.
MyServerName J, and click Modify.
In the Volume Properties dialog box, click Locate and select your Jobs drive,
the ellipses beside Path and select your usually drive J.
Jobs drive, usually drive J.
Click Make New Folder and type the Click Make New Folder and type the
shared folder name, for example, shared folder name, for example,
AraxiVolume. Click OK twice. AraxiVolume. Click OK.
When asked if you want to restart the In the Volume Properties dialog box,
volume, click Yes and click Restart. type the Volume Name of the
Prinergy share, for example, Jobs
on MyServerName J. Click OK.
Next: Stop and restart Prinergy for these changes to take effect.
See also:
Converting to AFP on page 128
1. Locate %AraxiHome%\etc\otherhosts.
2. Open the otherhosts file in a text editor.
3. Locate the [/etc/otherhosts] section, and add
"*:MyServerName"="MyServerName" as the third line.
[/etc/otherhosts]
"SOMEZONE:blatserver1"="NTBLATSERVER1"
"SOMEZONE:blatserver2"="NTBLATSERVER2"
"*:MyServerName"="MyServerName"
Example
In this example:
● The tertiary server is called "TertiaryServer" and it is
configured in the Mac Zone "Prinergy Lab".
● The first volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Mac computers.
● The second volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Windows 2000-based computers.
● The Mac share name is "Jobs on TertiaryServer".
● The Samba share name is "AraxiVolume_TertiaryServer".
[/etc/otherhosts]
"Prinergy
Lab:TertiaryServer"="TertiaryServer"
[shares]
NtHost="TertiaryServer"
"Jobs on
TertiaryServer"="AraxiVolume_TertiaryServer"
"AraxiPreps"="AraxiPreps"
See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128
78 Chapter 6—Servers
Requirements:
● Using a Brisque server as a tertiary server requires SMB.
● Upgrade all Prinergy servers to Prinergy 3.1.0.7 or later.
● If the Hummingbird® NFS Maestro® Client software or SFU (Services
for UNIX) software is installed on the Prinergy primary server, uninstall
it.
1. Create a user account for the Araxi service and give it the name Araxi.
2. Give the user account full permissions to the directory being shared
and to all files and subdirectories under it. Use either of the following
methods:
● Add the user account to a group that has the required permissions,
such as the local administrator group.
● Give the permissions directly to the user account.
For information about assigning permissions in UNIX, see the UNIX
documentation.
● Install Samba.
Follow the instructions in the Samba for Brisque 4.1, Brisque 5, and Brisque
Serve Installation and Configuration Guide.
RPC calls to the SFM service on the server. These calls occur
frequently—for example, every time a page is refined. Although the
calls eventually time out, they affect Prinergy performance.
1. Locate %AraxiHome%\etc\otherhosts.
2. Open the otherhosts file in a text editor.
3. Locate the [/etc/otherhosts] section, and add
"*:MyServerName"="MyServerName" as the third line.
[/etc/otherhosts]
"SOMEZONE:blatserver1"="NTBLATSERVER1"
"SOMEZONE:blatserver2"="NTBLATSERVER2"
"*:MyServerName"="MyServerName"
Example
In this example:
● The tertiary server is called "TertiaryServer" and it is
configured in the Mac Zone "Prinergy Lab".
● The first volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Mac computers.
● The second volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Windows 2000-based computers.
Adding a tertiary server or input volume to the system 83
See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128
Requirements:
Install or set up the following items:
● Prinergy 3.1.0.7 or later on the Prinergy servers (primary and
secondary)
● Mac OS X Samba 3.0.6 or later on the Apple Xserve server (tertiary)
● Mac OS X Server 10.3.9 or later on the Apple Xserve server (tertiary)
● TCP/IP
Important: Kodak does not provide direct support for UNIX servers that
are used as Prinergy tertiary servers, unless the UNIX computer is using
the Brisque or Brisque Serve software. Limited support for non-Kodak
servers is available in this guide.
Creating an Araxi service account on an Xserve server
Create an Araxi service account on the Xserve tertiary server to enable
Prinergy server components to access all necessary resources on the
tertiary server.
1. On the Xserve server, create a folder that you want to share and that
is accessible to the Prinergy primary server. For example, create a
folder named AraxiVolume_MyServerName.
2. In the Workgroup Manager software, click Sharing.
3. Click the All tab, and select the folder that you want to share with the
Prinergy primary server.
4. Click the General tab, and select the Share this item and its contents
check box.
5. In the Owner box, type Araxi, and select Read & Write permissions.
6. In the Group box, type Prinergy, and select Read & Write permissions.
Configuring an Xserve server with SMB 87
Then in the Xserve server's Server Manager, restart the Windows service.
88 Chapter 6—Servers
1. Locate %AraxiHome%\etc\otherhosts.
2. Open the otherhosts file in a text editor.
3. Locate the [/etc/otherhosts] section, and add
"*:MyServerName"="MyServerName" as the third line.
[/etc/otherhosts]
"SOMEZONE:blatserver1"="NTBLATSERVER1"
"SOMEZONE:blatserver2"="NTBLATSERVER2"
"*:MyServerName"="MyServerName"
Example
In this example:
● The tertiary server is called "TertiaryServer" and it is
configured in the Mac Zone "Prinergy Lab".
● The first volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Mac computers.
● The second volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Windows 2000-based computers.
90 Chapter 6—Servers
See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128
Requirements:
● Determine whether the Prinergy system uses SMB or AFP file-sharing
protocol. SMB is recommended.
● If the Hummingbird NFS Maestro Client software or SFU (Services for
UNIX) software is installed on the Prinergy primary server, uninstall
it.
Important: Kodak does not provide direct support for UNIX servers that
are used as Prinergy tertiary servers, unless the UNIX computer is using
the Brisque or Brisque Serve software. Limited support for non-Kodak
servers is available in this guide.
1. Create a user account for the Araxi service and give it the name Araxi.
2. Give the user account full permissions to the directory being shared
and to all files and subdirectories under it. Use either of the following
methods:
● Add the user account to a group that has the required permissions,
such as the local administrator group.
● Give the permissions directly to the user account.
For information about assigning permissions in UNIX, see the UNIX
documentation.
Installing connectivity software on a generic UNIX server 93
Note: If you find performance to be slow, changing the protocol may improve
performance. Change the three protocol lines as indicated below.
# Samba config file created using SWAT
# from 10.1.66.51 (10.1.66.51)
# Date: 2004/05/04 08:55:15
# Global parameters
[global]
workgroup = MYWORKGROUP
netbios name = CREOLINUX
server string = %h server (Samba %v)
encrypt passwords = Yes
update encrypted = Yes
map to guest = Bad User
obey pam restrictions = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n.
syslog = 0
log file = /var/log/samba/log.%m
max log size = 50
protocol = LANMAN2
max protocol = LANMAN2
min protocol = LANMAN2
time server = Yes
UNIX extensions = Yes
mangling method = hash2
preferred master = No
local master = No
domain master = No
browse list = No
enhanced browsing = No
dns proxy = No
invalid users = root
create mask = 0777
case sensitive = No
# Example shared volumes. Prinergy requires the
# AraxiVolume_xxx naming format to use the # shared
# volume as a job share.
[AraxiVolume_P3Linux_18gb]
comment = 18GB Volume on P3Linux
path = /18gb
read only = No
[AraxiVolume_P3Linux_36gb]
comment = 36GB Volume on P3Linux
path = /36gb
read only = No
1. On the tertiary server, create the folder that you will share.
Adding a server to the HOSTS file of the other servers 95
● Perform this task to identify all non-SFM servers (that is, servers not
using Microsoft Services for Macintosh) in your system with any Mac
client computer protocols—not only with AFP.
● This task applies whenever you configure Mac client computer
protocols.
● Prinergy performance suffers unless you ensure that all non-SFM
servers are listed in the OTHERHOSTS file. Otherwise, Prinergy makes
RPC calls to the SFM service on the server. These calls occur
frequently—for example, every time a page is refined. Although the
calls eventually time out, they affect Prinergy performance.
1. Locate %AraxiHome%\etc\otherhosts.
2. Open the otherhosts file in a text editor.
3. Locate the [/etc/otherhosts] section, and add
"*:MyServerName"="MyServerName" as the third line.
[/etc/otherhosts]
"SOMEZONE:blatserver1"="NTBLATSERVER1"
"SOMEZONE:blatserver2"="NTBLATSERVER2"
"*:MyServerName"="MyServerName"
Example
In this example:
● The tertiary server is called "TertiaryServer" and it is
configured in the Mac Zone "Prinergy Lab".
● The first volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Mac computers.
● The second volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Windows 2000-based computers.
● The Mac share name is "Jobs on TertiaryServer".
● The Samba share name is "AraxiVolume_TertiaryServer".
[/etc/otherhosts]
"Prinergy
Lab:TertiaryServer"="TertiaryServer"
[shares]
NtHost="TertiaryServer"
"Jobs on
TertiaryServer"="AraxiVolume_TertiaryServer"
"AraxiPreps"="AraxiPreps"
See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128
3. If you intend to use the tertiary server for archiving, archive, purge,
and retrieve a job from the tertiary server.
Monitoring servers
Use the left pane of the Administrator window to monitor primary and
secondary servers in your Prinergy system. The left pane is always
displayed.
● Use the following table to interpret the information displayed in the
left pane about primary and secondary servers in your Prinergy system:
Column Possible Entries
Numeric release number plus update (if applicable), in A.B.X.Y for m, where:
A.B is the major and minor release of the product.
Version
X.Y is the major and minor update of the product.
For example, 2.0.5.1 indicates Prinergy release 2.0, update 5.1.
Removing a server
Remove a server from the Prinergy system when you no longer need the
server.
Secondary server Click the Servers tab, and select the server
from the Secondary Servers list.
Tertiary server Click the Servers tab, and select the server
from the Tertiary Servers list.
Kodak Veris™ or Matchprint Click the Veris/Matchprint tab, and select the
Virtual software server server.
Next:
Update the HOSTS file.
If you are not using folders to organize your accounts, the Araxi
service account is typically under Users.
d. If you are re-creating the araxi service user account, right-click the
old Araxi service account, select Delete, and click Yes to confirm.
e. Right-click the folder that will contain the Araxi service account,
select New > User, and follow the prompts.
Clear the User must change password at next logon check box.
1. Log on as an administrator.
Changing server configurations 105
Tertiary server Mac client computer protocol Service level and comments
Windows Server 2000 and Windows Either of the following protocols: ● Service level 1, if the server is
Server 2003 purchased from Kodak
● AFP with SFM
● Service level 3, if the server is
● AFP with ExtremeZ-IP
not purchased from Kodak
We are working to qualify this operating
system for SMB with ADS, if all Mac client
computers run Mac OS X 10.5. Do not use
SMB with ADS until it is qualified.
Tertiary server Mac client computer protocol Service level and comments
Mac OS X Server 10.4 SMB with AppleDouble Service level 2 until Mac OS X
Server 10.5 is qualified.
Service level 3 after Mac OS X
Server 10.5 is qualified.
Mac OS X Server 10.5 Qualified for AFP for Prinergy 4.1.2.2 and Service level 2, when this solution
higher. is qualified
Not yet qualified for any other protocol
Brisque Server, which uses Samba AFP via Helios Service level 1
and Helios
Archiving is not supported.
UNIX with Samba and an AFP server, AFP via the AFP server Service level 3
such as Helios or Xinet
Archiving is not supported.
UNIX with Samba and no AFP server SMB with AppleDouble Service level 3
Service level 3 The solution is documented but not tested with every major
upgrade and not supported. Support is limited to
documentation.
A problem will be investigated only if it meets the following
conditions:
● The problem is caused by Prinergy.
● The problem can be replicated on a job volume on the
customer's Prinergy primary server. The customer must
keep the job volume on the primary server for this purpose.
After a Prinergy upgrade, you must confirm that the solution
still works to your satisfaction. Consider buying a software
testing solution to test upgrades before implementing them
on a production system. For information about testing
solutions, contact your sales representative.
AFP
Apple Filing Protocol, which is built into the Mac OS
On Windows servers, AFP can be implemented via SFM or
ExtremeZ-IP. On UNIX servers, AFP can be implemented with
Helios, Xinet, and other software.
AFP stores file resources in resource forks.
NFS
Network File System, which is built into the UNIX operating
system
On Windows servers, NFS can be implemented with SFU.
AFP
The main limitation of all AFP servers is that archiving is not supported on tertiary
servers using UNIX or on tertiary servers using Mac OS X 10.4 or earlier. Although
the files are archived, the resource forks are lost.
112 Chapter 7—Mac client computer protocols
NFS
NFS is not qualified for use with Prinergy, so its limitations are not relevant.
See also:
File resources on page 112
File resources
The Mac OS and the Windows operating system store file resources in
different ways.
See also:
Limitations of Mac client computer file-sharing protocols on page 111
Resource forks
Resource forks store file resources in the file itself.
The Hierarchical File System (HFS) of the Mac OS uses resource forks.
AppleDouble
UNIX file systems can store Mac OS-compliant resources with the AppleDouble
file format, which places resources in a separate file with the same file name as
the data file but prefixed with "._". For example, a file named input.pdf has
a corresponding AppleDouble file named ._input.pdf.
Other
Other platforms, such as EtherShare and Xinet, store resources in separate files
with special file name extensions.
See also:
Converting to AFP on page 128
b. Click the Security tab, and confirm that the following check boxes
are cleared.
● Allow Workstations to Save Password
● Show Only Accessible Volumes
● Reset Permission on Moves (Global)
● Notify Mac Clients of Password Expirator
● Enable IPv6
c. Click the Search tab, and confirm that the Use lazy indexing check
box is cleared.
d. Click the Filename Policy tab, and confirm that all of the check
boxes are cleared.
e. Click the Service Discovery tab, and confirm that the Zidget/HTTP
check box is cleared.
Important: The Server Name must not have IP at the end of the
server name. Otherwise the server will appear twice in the Finder.
f. Click OK.
7. If you are installing on a primary or secondary server, and you migrated
shares, follow the left column to modify the path of the volume.
If you are installing on a tertiary server, and you did not migrate shares,
follow the right column to create an ExtremeZ-IP share for Prinergy.
When creating shares, ensure you follow these conventions:
● The Windows Share Name must start with AraxiVolume_ and must
use the same folder path as the ExtremeZ-IP share.
● The AFP and ExtremeZ-IP Volume Name cannot exceed 27
characters.
● If you have existing jobs and are adopting ExtremeZ-IP, do not
change share names.
118 Chapter 7—Mac client computer protocols
In the Volumes dialog box, select the Jobs In the Volumes dialog box, click
on J drive volume, for example, Jobs on Create.
MyServerName J, and click Modify.
In the Volume Properties dialog box, click Locate and select your Jobs drive,
the ellipses beside Path and select your usually drive J.
Jobs drive, usually drive J.
Click Make New Folder and type the Click Make New Folder and type the
shared folder name, for example, shared folder name, for example,
AraxiVolume. Click OK twice. AraxiVolume. Click OK.
When asked if you want to restart the In the Volume Properties dialog box,
volume, click Yes and click Restart. type the Volume Name of the
Prinergy share, for example, Jobs
on MyServerName J. Click OK.
Next: Stop and restart Prinergy for these changes to take effect.
See also:
Converting to AFP on page 128
1. Locate %AraxiHome%\etc\otherhosts.
2. Open the otherhosts file in a text editor.
3. Locate the [/etc/otherhosts] section, and add
"*:MyServerName"="MyServerName" as the third line.
[/etc/otherhosts]
"SOMEZONE:blatserver1"="NTBLATSERVER1"
"SOMEZONE:blatserver2"="NTBLATSERVER2"
"*:MyServerName"="MyServerName"
Example
In this example:
● The tertiary server is called "TertiaryServer" and it is
configured in the Mac Zone "Prinergy Lab".
● The first volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Mac computers.
● The second volume name after the Mac Zone ("Prinergy
Lab:TertiaryServer"="TertiaryServer") is the UNIX server
name that appears on Windows 2000-based computers.
● The Mac share name is "Jobs on TertiaryServer".
● The Samba share name is "AraxiVolume_TertiaryServer".
[/etc/otherhosts]
"Prinergy
Lab:TertiaryServer"="TertiaryServer"
[shares]
NtHost="TertiaryServer"
"Jobs on
TertiaryServer"="AraxiVolume_TertiaryServer"
"AraxiPreps"="AraxiPreps"
See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128
Updating the SFMHOSTS file 121
Next: Stop and restart Prinergy for these changes to take effect.
Any version Add the Mac client computer to the same domain as the Prinergy primary server.
Mac OS X Add the primary server to the NetInfo™ Manager of the Mac client computer:
10.3 or 10.4
1. Log on to the Mac client computer with an administrator account.
2. In Finder, click Go > Utilities.
3. Double-click NetInfo Manager.
4. Click machines.
5. From the Security menu, choose Authenticate, and type the password of the administrator
account. If Deauthenticate is available, skip this step because you are already authenticated.
6. From the Directory menu, choose New Subdirectory.
7. In the lower pane, double-click new_directory, and type the name of the Prinergy primary server.
8. From the Directory menu, choose New Property, and then replace new_property by typing
ip_address.
9. Double-click new_value, and replace it by typing the IP address of the Prinergy primary server.
10. From the Domain menu, choose Save Changes, click Update this copy, and then quit NetInfo
Manager.
Mac OS X Add the primary server to the hosts file of the Mac client computer:
10.5 or later
1. Log on to the Mac client computer with an administrator account.
2. In Finder, click Go > Utilities.
3. Double-click Terminal.
4. In the Terminal dialog box, type sudo nano /etc/hosts
5. If you are prompted for a password, type your password.
6. Add the IP address of the Prinergy primary server in the following format:
ip hostname
7. Press Ctrl+X, press Y to save your changes, and press Enter to save the file in the /etc folder.
See also:
Converting to SMB with AppleDouble on page 124
Changing Mac client computer file-sharing protocols 123
If you use VERITAS and you do not need to copy files to a primary or secondary
server (because you store files only on tertiary servers), you can manually convert
protocols.
The DoubleTake software offers several advantages over VERITAS. For
information, see the Prinergy Emergency Platemaking Plus (EPM+) With
Double-Take® User Guide.
3. If you use SFM to support AFP, stop and disable the SFM services on
all Windows operating system servers in the Prinergy system:
a. Right-click My Computer and select Manage.
b. In the Computer Management window, expand Services and
Applications and click Services.
c. In the right pane, right-click File Server for Macintosh and select
Properties.
d. Click Stop.
e. In the Startup type list, select Disabled and click OK.
f. In the right pane, right-click Print Server for Macintosh and select
Properties.
g. Click Stop.
h. In the Startup type list, select Disabled and click OK.
When SFM stops, all AFP shares are deleted, so there is no need
to manually remove AFP mappings.
4. If you use ExtremeZ-IP to support AFP, uninstall it. Click Start >
Programs > ExtremeZ-IP > Uninstall ExtremeZ-IP File Server and
follow the prompts to uninstall ExtremeZ-IP.
5. In Prinergy Administrator, from the Tools menu, select File Sharing.
If File Sharing is not available, verify that you met the requirements
at the start of this procedure.
The File Sharing dialog box appears, listing the names of every server
and input volume in the Prinergy system, including the volumes on all
servers listed on the Servers and Input Volumes tabs.
6. In the File Sharing dialog box, select all Windows volumes that contain
job data:
● If a volume uses Windows and contains jobs, select it. All Windows
job volumes must be converted at the same time.
● If a volume uses Windows but does not contain jobs, you do not
have to select it. Select it only if it contains files that you want to
126 Chapter 7—Mac client computer protocols
9. If errors occur, a message appears, telling you to view the log file:
a. Click OK to close the error message.
b. In the %AraxiHome%\CreoAraxi\System folder, open the
forktranslator.log file in Notepad.
c. If the log identifies job files that were not converted, locate the
original job file from a backup or other source, and copy the file to
the volume.
Resources are created automatically when you copy the file.
10. If you have a job volume on a UNIX server that also has an AFP server,
such as the Xinet software or the HELIOS™ software, use a Mac OS X
computer to convert the files on the UNIX volume to SMB:
a. Use a Mac computer running Mac OS X to connect to the UNIX
volume via AFP.
b. Copy the files from the UNIX volume to another location, such as
the Mac computer.
c. Disable the AFP server on the UNIX volume.
Changing Mac client computer file-sharing protocols 127
If you do not disable ADS, any client computers with Mac OS X 10.5
may connect to the server via alternate data streams, not AppleDouble.
13. Verify that all non-SFM servers are identified in OTHERHOSTS files.
14. Perform either of the following tasks to complete the conversion:
● If you stopped Prinergy, restart it.
● If you stopped the Archive/Retrieve JTP and Purge JTP, start them.
If you use integrated Preps on Mac client computers that are not in the same
domain as the primary server, enable Preps under SMP.
128 Chapter 7—Mac client computer protocols
If you add a new volume to the Prinergy system after you convert protocols, files
on that volume will not contain resource information. If you want resources for
files on the new volume, manually convert the files' resources to AFP format.
See also:
Identifying non-SFM servers in the OTHERHOSTS file on page 119
Enabling Preps under SMB on page 121
Converting files with Fork Translator on page 133
Converting to AFP
Use Prinergy Administrator to change the Mac-sharing protocol of
Prinergy and files on job volumes from SMB to AFP with AppleDouble.
Requirements:
● The protocol that you want to adopt must be qualified for the servers
in your Prinergy system.
● All Prinergy server and client computers must be successfully updated
to Prinergy 3.1.0.7 or later.
● VERITAS Storage Replicator (VSR) software must not be installed in
the Prinergy system.
● Plan for down time ranging from one to several hours, depending on
the size of your volumes. For example, after you shut down the required
software, converting a volume that contains 10,000 files takes two to
three minutes.
Use this procedure if your system includes one or more Windows job
volumes. If your system has only UNIX, XServe, or Isilon servers, you
must manually convert the system, which does not require you to stop
the Prinergy system.
9. If errors occur, a message appears, telling you to view the log file:
a. Click OK to close the error message.
b. In the %AraxiHome%\CreoAraxi\System folder, open the
forktranslator.log file in Notepad.
c. If the log identifies job files that were not converted, locate the
original job file from a backup or other source, and copy the file to
the volume.
Resources are created automatically when you copy the file.
10. If you have a job volume on a UNIX server with an AFP server, such
as the Xinet software or the HELIOS software, use a Mac OS X
computer to convert the files on the UNIX volume to AFP:
a. Use a Mac computer running Mac OS X to connect to the UNIX
volume via SMB.
b. Copy the files from the UNIX volume to another location, such as
the Mac computer.
c. Enable the AFP server on the UNIX volume.
d. Use a Mac computer running Mac OS X to connect to the UNIX
volume via AFP.
e. Copy the files back to the UNIX volume, but place them in a
different folder
If the files contain resource information, resource forks are created
during the copying process.
f. Delete the original files.
11. If you have a job volume on a server running Mac OS X Server 10.4,
use third-party software called Fork Server Helper to convert the
Xserve volume.
The demonstration version of Fork Server Helper is free to use.
a. Contact your service representative or visit the Marcel Bresink
Software-Systeme (MBS) Web site at
http://www.bresink.de/osx/ForkServerHelper.html to get Fork Server
Helper and information about it.
b. Use Fork Server Helper to convert the files on the Xserve volume.
12. Verify that all non-SFM servers are identified in OTHERHOSTS files.
13. Perform either of the following tasks to complete the conversion:
● If you stopped Prinergy, restart it.
● If you stopped the Archive/Retrieve JTP and Purge JTP, start them.
Manually converting protocols 131
If you add a new volume to the Prinergy system after you convert protocols, files
on that volume will not contain resource information. If you want resources for
files on the new volume, manually convert the files' resources to AFP format.
See also:
Starting SFM to support AFP on page 114
Configuring AFP with ExtremeZ-IP on page 115
Identifying non-SFM servers in the OTHERHOSTS file on page 119
If you do not disable ADS, any client computers with Mac OS X 10.5
may connect to the server via alternate data streams, not AppleDouble.
7. Verify that all non-SFM servers are identified in OTHERHOSTS files.
See also:
Converting files with Fork Translator on page 133
where
134 Chapter 7—Mac client computer protocols
-a
Create resource fork information from alternate data streams
(ADS) to AppleDouble files.
-s
Create resource fork information from AppleDouble files to
alternate data streams (ADS).
-h
Print this usage information.
-i
Ignore errors and keeps processing other files.
-n
Do not execute. Lists file names only.
-e
Exclude the specified folders, separted by semicolons.
-o
Overwrite any existing fork information in AppleDouble files or
alternate data streams (ADS), if present .
-p
Print progress to the screen.
-v
Write to standard output (stdout) files. Implied by -n.
pathname...
Operate on the specified files and/or folders, separated by spaces.
Folders are treated recursively.
See also:
Converting to SMB with AppleDouble on page 124
Manually converting protocols on page 131
Troubleshooting
Refer to this section if you have trouble running ExtremeZ-IP.
If you cannot see your shares and you get this message in the Windows system
event log: Failed to initialize AppleTalk support (10049). The
ExtremeZ-IP server will not appear in the Chooser, modify your
registry.
Changing Mac client computer file-sharing protocols 135
See also:
Determining if a third-party proofing device can be used with Prinergy
on page 140
140 Chapter 8—Proofing devices
1. Determine what file formats the proofing device accepts. Refer to the
manufacturer's manual for the device, or the manufacturer's Web site.
Note: Proofing devices that use built-in RIPs often have a proprietary
format (for example, the Epson ESC/P2, HP HPRTL, and Canon® GARO
printer control languages). Proofing devices that use external RIPs
often accept the Adobe PostScript language, PDF, TIFF, and sometimes
JPEG.
3. Confirm that the Prinergy software can output a file formats that the
proofing device accepts. For a list of supported output formats, see
your Prinergy Workshop Help.
Note: It is best to send raster output to the proofing device (for
example, EPS raster, DCS raster, CT, or TIFF). Although sending vector
output is faster, a raster format ensures that you use the same RIP to
make the proof as to make a plate. The integrity of the data is
maintained and you avoid any inconsistency between RIP brands or
versions.
print queue on the proofing device (or its host computer) to test
basic connectivity to the network.
● If the file formats do not match, you can purchase a third-party RIP.
142 Chapter 8—Proofing devices
A flowchart to help you to assess whether you can use your third-party
proofing device with Prinergy
1. Create a shared folder to store the PPD files and PPX files that describe
the plate types available to each output device.
a. On the desktop, right-click My Computer and select Manage.
b. In the Computer Management window, in the left pane, double-click
Shared Folders to expand the tree.
c. Right-click Shares and select New File Share.
d. In the Create Shared Folder dialog box, click the Browse button,
and then select the folder that you want to share.
This share must reside on an NTFS volume, or an error message
will appear when you create the share.
e. In the Accessible from the following clients box, select the
Microsoft Windows check box.
f. If your Prinergy system includes Mac client computers, select the
Apple Macintosh check box.
g. In the Share name box, type a name for the share, such as Prinergy
PPDs.
h. If you selected the Apple Macintosh check box, in the Macintosh
share name box, type the same name that you typed in the Share
Name box.
i. Click Next, click Finish, and click No to indicate that you do not
want to create another share.
j. Close the Computer Management window.
146 Chapter 9—Adding output devices
3. In your imposition software, add the output device and set the device
configuration, if necessary.
See the documentation for the imposition software.
4. Copy the PPD files to the computer where you've installed the
imposition software:
a. On the computer with the imposition software, mount the PPD
folder on the Prinergy primary server.
b. Copy the PPD and PPX files from Prinergy PPD folder to the
imposition software PPD folder.
5. Test the setup of the new device:
a. In your imposition software, create an imposition plan for a test
plate.
See the documentation for the imposition software.
b. In the Workshop software, import the imposition plan.
c. In the Workshop software, create a process template for the output
device.
d. In the Workshop software, image media on the output device using
the new process template.
10 Digital printers
Set up digital printers as workflow processors so that you can use these
in Workshop. For more information about digital printers, see Workshop
Help.
1. From the Managed Connections menu, select Add, and then select
the digital printer that you want to add—for example, Kodak NexPress.
If the digital printer that you want to add is not listed, click Other Digital
Print Controller.
2. Type the server name or address, and click Add.
In Prinergy Administrator, each digital printer is listed on the Managed
Connections tab in the right pane.
In Job Manager, each digital printer is listed on the Process menu and in the
Process Templates pane on the Global tab. You can use the process templates
listed under the digital printer that you added, just like any other process template.
For information on using process templates, see Workshop Help.
1. On the Managed Connections tab in the right pane, select the digital
printer that you want to delete.
2. From the Managed Connections menu, select Remove.
3. Click OK.
11 RBA setup
If you use Rules-Based Automation (RBA), you must configure user rights,
file transfer settings, and e-mail.
6. Send a test message with RBA to make sure e-mail is set up correctly:
a. Click Test.
b. Enter your e-mail address.
c. Click Send Test E-mail, click Close, and click OK.
d. Check your e-mail messages to make sure that you received the
message from RBA.
Note: Even if you receive the test message, RBA e-mail is not set
up until you perform the next step.
Next:
If you changed the default e-mail address for RBA, the new address takes
effect on each client computer only after the Workshop is restarted. All
other changes take effect immediately.
Next:
You are now ready to set up e-mail service for RBA.
● For Windows client computers, go to the proxy server and add the IP
address of the Prinergy primary server as an exception to the proxy
list.
12 Preferences
Control how hot folders work, how long certain data is kept, default settings
in Workshop, and many other preferences.
RIPs
Prinergy includes two RIPs for creating PDF files: the existing Adobe CPSI
and the new Adobe PDF Print Engine.
Important: The Adobe PDF Print Engine RIP is in beta until further notice,
but it is available for testing purposes. Do not use it for production
purposes.
Because there are two RIPs in the Prinergy system, you need to use
Administrator to:
● Identify the RIP that all new jobs use by default. If you decide to use
the non-default RIP for specific jobs, open the job in the Workshop
software and select the RIP in the Job Attributes dialog box.
● Control whether a plate can be generated with a different RIP than the
RIP used for the proof. You can prevent the plate from being producted,
or you can just receive a warning. If you want to change this setting on
a specific job, open the job in the Workshop software and change the
setting in the Job Attributes dialog box.
Choosing a RIP
Because Adobe PDF Print Engine is a PDF RIP, files remain in PDF throughout
processing. The RIP does not consume PostScript language objects, and it does
not flatten PDF files to the PostScript language before processing, like the CPSI
RIP does.
The Adobe PDF Print Engine RIP provides the following advantages over the CPSI
RIP:
● Adobe PDF Print Engine accurately handles files with native transparency
without flattening. If a file exposes a problem in the flattener or in the CPSI
RIP, the Adobe PDF Print Engine can handle the file correctly.
● Adobe PDF Print Engine’s rendering of fonts is more like the Acrobat software’s
rendering of fonts.
● Adobe PDF Print Engine correctly renders text that is located below transparent
images. Occasionally, when low-resolution proofs are rendered by the CPSI
RIP, the text appears fatter due to the flattening that occurs in CPSI. Because
Adobe PDF Print Engine does not flatten, it does not have this problem.
156 Chapter 12—Preferences
The disadvantages of using the Adobe PDF Print Engine RIP include the following
items:
● Adobe PDF Print Engine cannot process PDF files containing embedded
PostScript language objects, including pages that were processed with
PostScript bypass or with OPI bypass features of Prinergy.
● In some cases, Adobe PDF Print Engine processes copydot data and separated
pages more slowly than the CPSI RIP.
● Because it is a new (beta) product, you may experience problems with it.
See also:
Selecting the default RIP for new jobs on page 156
4. From the Final Output Handling When Proof RIP is Different list,
select Warn when Proof RIP is different or Fail when Proof RIP is
different.
5. Click OK.
All new jobs will use the settings that you specified. Existing jobs remain
unaffected.
Signature ID codes
Signature ID codes are marks that identify--in alphanumeric or barcode
format--which signature the sheet will be used for. Signature ID codes,
which can include version and section information, are typically printed
on the spine area in barcode format so that automatic binding machines
can read the codes and put the signatures together in the correct order.
Signature ID codes 157
You can set up and place signature ID codes in the following ways:
● Use imposition software, such as Preps, to create and place the code
as a Prinergy variable mark.
● Use the signature ID code in a Prinergy sheet mark or slug line mark.
See also:
Controlling how long history logs are kept on page 161
Compressing the database on page 220
All History
How many days history entries are kept before they are
Entries
permanently deleted from the Prinergy system. You can
configure your system to delete non-essential history entries
on a regular basis.
The default setting is 99999, which means logs are kept
indefinitely.
Database
How many days database reports are kept before they are
Reports
purged from the Prinergy system
Entries
The default setting is 99999, which means logs are kept
indefinitely.
Non-Essential
How many days non-essential history entries are kept before
History Entries
they are deleted from the Prinergy system. These entries are
predetermined by the system; you can't specify which entries
are non-essential.
The default setting is 30 days.
162 Chapter 12—Preferences
Setting Specifies
4. Click OK.
Job folders
A job folder is a folder on a Prinergy server that contains all the system
files for a job.
In addition, a job folder may contain any input files from your customer
and any user-defined subfolders. Job folders are stored in a central
directory on a primary, secondary, or tertiary server.
When you create a job, the server and volume where the job is stored.
Prinergy-generated files related to the job—for example, PDF masters and thumbnails
System Important: Do not modify the system files in any way; doing so may affect Prinergy's
ability to reference your job and its components.
Files that control job processing—for example the APA (Advanced Product Automation)
Control
file
Files that have been uploaded by InSite software users—for example, software files or
WebUpLoads
graphics files for a job
Folders automatically created by Prinergy when creating a new job. These folders are
UserDefinedFolders
generally used for storing input files. You can configure these folders.
See also:
Defining custom job folders on page 163
Add a folder
a. Click the button.
b. In the New Folder box, type the folder name that you
want Prinergy to automatically create when it creates a new
job, and then press enter.
4. Click OK.
Changes you make affect new jobs only—not existing jobs.
164 Chapter 12—Preferences
Group Size
The number of files that are processed together when files are dropped into a hot folder.
Grouping files reduces the number of active tasks, which reduces processing overhead and
can speed up processing.
For example, if Group Size is set to 1 and you drop 1000 files into a hot folder, each file is
processed individually. Icons representing the 1000 processes appear in the Active Processes
pane of Job Manager in the Prinergy Workshop software, and 1000 messages appear for the
job in the History view. Likewise, if Group Size is set to 200 and you drop 1000 files into a
hot folder, five processing groups are created, icons representing the five groups appear in
the Active Processes pane, and five messages appear for the job in the History view.
The default Group Size setting is 200.
Wait Time
The number of seconds that the Prinergy system waits after a file is dropped into a hot folder
Between Dropped
before creating a group
Files
If the time specified as the Wait Time Between Dropped Files has elapsed, the Prinergy
system concludes that no more files are coming and it creates a group, even if fewer files than
the Group Size number have been dropped into the hot folder.
The default Wait Time Between Dropped Files setting is 20 seconds.
Controlling the error messages that Prinergy displays 165
Setting Specifies
Wait Time
The number of seconds that the Prinergy system waits for the master file of a multi-file set to
Between Dropped
be dropped into a hot folder
Files of a Multi
File Set When you drop files from a multi-file set into a hot folder, if the file format does not indicate
that the file is part of a multi-file set, the Prinergy system waits for the number of seconds
specified in the Wait Time Between Dropped Files of a Multi File Set option. If the master
file is not dropped into the hot folder within this time, the files are submitted for processing
as individual files. After the master file is dropped into a hot folder, the Prinergy system knows
which files belong to the multi-file set. The set is not submitted for processing until all files
are in the hot folder.
If the file format indicates that an input file is part of a multi-file set (for example, TIFF-IT),
Wait Time Between Dropped Files of a Multi File Set is not applied to the files. The set is not
submitted for processing until all files are in the hot folder.
A multi-file set can be DCS 1, multi file DCS-2, CT/LW, or TIFF/IT.
The default Wait Time Between Dropped Files of a Multi-File Set setting is 20 seconds.
Group Type
Options for Group Type are:
All Single File Formats: If this option is selected, PostScript, EPS, PDF, and TIFF files are
grouped.
None: If this option is selected, files are not grouped. All files are processed one at a time,
regardless of the Group Size setting.
PS, EPS, PDF: If this option is selected, PostScript, EPS, and PDF files are grouped.
The default Group Type setting is All Single File Formats.
4. Click OK.
5. Stop and restart Prinergy.
4. Click OK.
5. Stop and restart Prinergy.
7. Click OK.
8. Stop and restart Prinergy.
If this box is set to 0, Prinergy overwrites the PDF page files in the job folder each
time you re-refine an input file. If this box is set to a value greater than 0, Prinergy
keeps old revisions of PDF page files by renaming them in the format
file.p1.revN.pdf, where N represents the revision number. Previous
revisions are located in the System\SubPagesRevisioned folder.
Refine Result
file.p1.rev1.pdf is renamed
file.p1.rev2.pdf
3rd
file.p1.pdf is renamed file.p1.rev1.pdf
file.p1.pdf is generated
Administering Dashboard 169
Refine Result
file.p1.rev2.pdf is renamed
file.p1.rev3.pdf
file.p1.rev1.pdf is renamed
4th file.p1.rev2.pdf
file.p1.pdf is renamed file.p1.rev1.pdf
file.p1.pdf is generated
file.p1.rev3.pdf is deleted
file.p1.rev2.pdf is renamed
file.p1.rev3.pdf
5th file.p1.rev1.pdf is renamed
file.p1.rev2.pdf
file.p1.pdf is renamed file.p1.rev1.pdf
file.p1.pdf is generated
Administering Dashboard
By default, Dashboard shows the job status only from the primary Prinergy
server. Using DashboardAdmin, you can specify additional Prinergy
servers for Dashboard to monitor.
1. Go to http://<Prinergy server
name>/Dashboard/DashboardAdmin.html, where <Prinergy server
name> is the name of the Prinergy primary server.
2. Enter your user name and password, and click Login.
3. Add or delete the servers that Dashboard monitors:
To Do This
Add a Prinergy server In the text box at the bottom, type the Prinergy server
If (offline) appears after the server name, the server might be down,
running a different version of Prinergy, or inaccessible—for example,
due to access rights.
170 Chapter 12—Preferences
13 Monitoring
Daemons
Daemons are processes that runs behind the scenes to perform a specific
task. Daemons have no user interface; you do not interact directly with
them. Instead, you use the Prinergy Workshop software, which initiates
communication with the appropriate daemons.
A daemon allows processes (Workshop, tasks, files in hot folders, RBA,
and so on) to interact with a job. (Daemons are sometimes called servers,
but the Prinergy documentation reserves the word server for hardware.)
The file names of daemons appear in the Processes pane of Administrator
and in the Task Manager dialog box in the Windows operating system.
List of daemons
The following table lists most of the daemons that help run a Prinergy system.
Use this list if you encounter references to daemon executables in system
diagnostic logs.
Full Name
(Application File Name (Filename column) Description
column)
Automation
PAutomationD.exe Manages workflow templates
Daemon
Client Manager
PClientManagerD.exe Manages the Workshop software connections
Daemon
172 Chapter 13—Monitoring
Full Name
(Application File Name (Filename column) Description
column)
DFE Manager Integrates a Digital Front End (DFE), such as the Prinergy
PDfeManagerD.exe
Daemon Evo software, into the Prinergy system
Diagnostics View Reads and buffers log files written by the Diagnostic Log
diagserver.cmd
Daemon Daemon
Font Installation Lets users add a font to a job folder and enables the font
FINS.exe
Daemon to be converted to a RIP-ready (PDF) format
General File
PFileSummaryD.exe Retrieves summary information for imposition plans
Summary Daemon
Full Name
(Application File Name (Filename column) Description
column)
Job Launcher Opens the Job Daemon when a user opens a job in the
PJobLauncherD.exe
Daemon Prinergy Workshop software
JTP Agent Daemon PJtpAgentD.exe Starts and stops JTPs and tasks
License Key Monitor Monitors temporary licenses and issues a warning when
PLicMonD.exe
Daemon a temporary license is about to expire
Notification Server PNotificationServer.exe Notifies the Workshop software of changes on the server
Process Plan
PTaskTemplateD.exe Tracks the names and locations of process templates
Daemon
Registered File
PRegFileD.exe Records files and their locations to the database
Daemon
Rule Engine
AutomationApp.exe Executes rules in RBA
Daemon
Spool Daemon PSpoolServerD.exe A central repository for hot folder information and status
174 Chapter 13—Monitoring
Full Name
(Application File Name (Filename column) Description
column)
Workflow
WDSCServerD.exe Manages process templates
Descriptor Daemon
Workflow Manager
TWFMManagerD.exe Manages tasks
Daemon
Yoho Message Communicates data with the Kodak Link software, which
PYohoMessageServerD.exe
Server translates the data between an MIS and Prinergy
Retrieves work types and other data from Link for use
Yoho Proxy Server PYohoProxyServerD.exe
in the Workshop software
Viewing processes
Look in the Processes pane for information about processes, which include
JTPs and daemons.
Tip: The file names of daemons appear in the Processes pane of
Administrator and in the Task Manager dialog box in the Windows
operating system.
Server Which server the process is running Any server name in your Prinergy system
on
With third-party reporting software, you can run reports that are built in
to Prinergy or create custom reports.
4. In the Enter Values dialog box, filter the report and click OK.
The filters vary with each report. Examples include job name, date
range, and user name.
An ellipses (...) means a filter has not been set. To include all values,
select *.
178 Chapter 14—Database reports
See also:
Built-in reports on page 178
Built-in reports
Several database reports are available. The reports provide information
from the database, including information about archives, files, job status,
and job output.
Report title Description
Archive File Archived files, including the job name and file name
Filtered by file name
Archive Job Archived jobs, including the job name and the medium (tape) that each job is on
Locations
Filtered by job name.
Built-in reports 179
Archive Medium Media (tapes), including the medium name, its free and used capacity, the number of archives
Capacity it has, the first and last archive written on it, and its format
Summary information includes the total number of archives on all media
Filtered by date range and whether to include only the last instance of the medium or all instances
(including non-existent ones)
Archive Medium Media (tapes), including the medium name and the job names on the medium
Contents
Filtered by medium name
Find File File names, including the job name and full path of each file
Filtered by file name
Find Job Jobs, including each job's group, server, share, path, date created, and availability (online or
archived)
Filtered by job name, date range, and availability (online, archived, or both)
Job Create Destroy Jobs that have been created or destroyed, including the date when the job was created or
destroyed, the user who created or destroyed the job, whether the job was created or destroyed,
and the job name
Filtered by job name, user name, and date range
Job Final Output Plates that have been generated using a final output process template, including the job status,
Summary device, process template name, imposition name, signature number, sheet number, side number,
separation number, start and end time, duration, and approval status
Grouped by job group and then job name
Filtered by job name, date range, and one or more job statuses (such as Completed or On Press)
The job summary includes the total number of plates, number of approved plates, number of
rejected plates, total time, and average time per plate.
The report summary includes the total number of plates, total time, average time per plate, and
average time per job.
Job Imposed Page Impositions that have been output using an imposed output process template, including the job
Proof Summary status, device, process template name, imposition name, signature number, sheet number, side
number, separation number, start and end time, duration, and approval status
Grouped by job group and then job name
Filtered by job name, date range, and one or more job statuses (such as Completed or On Press)
The job summary includes the total number of proofs, number of approved proofs, number of
rejected proofs, total time, and time per proof.
The report summary includes the total number of proofs, total time, and average time per proof.
180 Chapter 14—Database reports
Job Loose Page Pages that have been output using a loose page output process template, including the job status,
Proof Summary device, process template name, page name, start and end time, duration, and approval status
Grouped by job group and then job name.
Filtered by job name, date range, and one or more job statuses (such as Completed or On Press)
The job summary includes the total number of proofs, number of approved proofs, number of
rejected proofs, total time, and time per proof.
The report summary includes the total number of proofs, total time, and average time per proof.
Job Status Jobs, including the job's server and share; status; who created it and when; number of input files,
Summary pages, and page proofs; when it was last archived, purged, and retrieved; and the following details
for each side of each sheet of each signature: the number of page positions and how many were
proofed, the number of separations and how many were proofed, whether all separations were
proofed, how many separations were plated, and the percentage of separations that were plated
Grouped by job group and then job name
Filtered by job name, date range, and one or more job statuses (such as Completed or On Press)
The imposition summary contains imposition totals for the same type of information that is in
the imposition section.
The job summary contains job totals for the same type of information that is in the imposition
section.
See also:
Running built-in reports on page 177
Note: Kodak does not provide direct support for Custom Database
Reporting. Support is limited to the CDBR documentation.
These instructions apply to Crystal Reports. If you are using other
reporting software, adapt the steps to match your software.
6. Select the views that you want to use in the report, move them to the
Selected Tables list, and then click OK.
CDBR uses database views, which are dynamic, virtual tables that
provide read-only access to the database. The CDBR views exactly
match the underlying database tables. The names of the views match
the tables, but they start with a RPT_ prefix (to indicate "reporting")
and end with a _V suffix (to indicate a "view"). The views and the
documentation about them are generated automatically from the
database.
To identify the views that contain the information you want, see the
Prinergy Custom Database Reporting documentation.
Next:
Create the report. For instructions on creating reports, see the
documentation for your reporting software.
See also:
Viewing database documentation on page 182
Interpreting history numbers on page 183
Character data in the database on page 184
underlying database tables. The names of the views match the tables,
but they start with a RPT_ prefix (to indicate "reporting") and end with
a _V suffix (to indicate a "view"). The views and the documentation about
them are generated automatically from the database.
Note: Kodak does not provide direct support for Custom Database
Reporting. Support is limited to the CDBR documentation.
See also:
Creating custom reports on page 180
Interpreting history numbers on page 183
Character data in the database on page 184
For example, if you search for 1001, you find the following line:
HistoryLog.Action.1001.String=Refining {0} input files using
the template {1}:{2}. Therefore, the description is Refining {0}
input files using the template {1}:{2}.
3. If the description contains parameters that are enclosed in curly braces
"{}", find the parameters:
a. Get the data from the HistLogParam1 column, and put it in place
of the {0} parameter.
b. Get the data from the HistLogParam2 column, and put it in place
of the {1} parameter.
c. Get the data from the HistLogParam3 column, and put it in place
of the {2} parameter.
d. Continue in this manner until you complete all parameters.
For example, if the values in the HistLogParam1, HistLogParam2, and
HistLogParam3 columns are 20, Refine, and 1stRef-Normz, the
description Refining {0} input files using the template
{1}:{2} becomes Refining 20 input files using the template
Refine:1stRef-Normz.
See also:
Creating custom reports on page 180
Viewing database documentation on page 182
Character data in the database on page 184
See also:
Creating custom reports on page 180
Viewing database documentation on page 182
Interpreting history numbers on page 183
186 Chapter 14—Database reports
15 Archiving
Disk Purge JTP Removes jobs or job files from the job’s
home server after verifying that they
were archived correctly. The process is
controlled by the Purge process template.
Removable storage devices (for archiving Tape libraries or tape drives that are
to tape) directly connected to the archiving
station
See also:
Adding JTPs on page 30
190 Chapter 15—Archiving
Archiving to disk
See also:
Setting up the Archiver on page 189
7. Manually copy the archived jobs from the old disk volume to the new
disk volume.
8. Restart the Archive\Retrieve and Purge JTPs: on the JTPs tab,
right-click the JTPs and select Start JTP.
See also:
Removing archive disk volumes on page 192
1. In Media Manager in Workshop, check that the disk volume that you
plan to remove does not contain any archived job data.
Important: If there are archived jobs on the disk volume, you will not
be able to remove it.
6. Click OK.
Note: An entry is added to system history to record the name of the
user who removed the disk volume.
See also:
Modifying archive disk volumes on page 191
Archiving to tape 193
Archiving to tape
box. If you do, the data on a tape will be lost if the tape is accidentally
de-allocated.
After the application pools are created, they are available for you to
target in archive, purge, and retrieve process templates in Workshop.
Tapes
Archiver supports MTF (Microsoft Tape Format) tapes, with the following
formats:
● AIT (Advanced Intelligent Tape)
Note: The WORM format is not supported.
Devices
You must use a device that has been qualified for use with Prinergy Archiver.
For a list of qualified devices, contact your service representative.
196 Chapter 15—Archiving
If you expect the data to span more than one tape, you must use a tape library.
Tape labels
Tapes used in the Archiver system must be clearly labeled with a unique
name.
You can label tapes with bar code systems or by hand.
Archiving to tape 197
Labeling by hand
If you label by hand, you must devise your own naming strategy. Make sure that
you:
● Use names with 64 or fewer characters
● Can add tapes without running out of names
● Use the same tape name in RSM and on the label. This makes it easier to
keep track of your archives and will help avoid accidently overwriting tapes.
Monthly One pool for the year, such as Create one archive and Every month, change the process
2008, 2009, and so on purge process template template to point to the pools for
that targets both pools for the current month.
Within the year pool, two
the current month.
pools for each month, such as
Jan_A, Jan_B, Feb_A, Feb_B,
and so on
Offsite Two application pools: Onsite Create one archive and Regularly move tapes from the
and Offsite purge process template Offsite pool to an offsite
that targets both the location—for example, weekly,
Onsite and Offsite pools. monthly, or when the tapes are full.
Monthly and One pool for the year, such as Create one archive and Every month, change the process
offsite 2008, 2009, and so on purge process template template to point to the pools for
that targets both the the current month.
Within the year pool, one pool
Onsite and Offsite pools
for each month, such as Jan, Regularly move tapes from the
for the current month.
Feb, and so on Offsite pool to an offsite
location—for example, weekly,
Within each monthly pool,
monthly, or when the tapes are full.
create an Onsite pool and an
Offsite pool
By customer Two pools for each customer, For each customer, create Each time you get a new customer,
such as Customer1_A, an archive and purge add pools and a process template
Customer1_B, Customer2_A, process template that for the customer.
Customer2_B, and so on targets both of the
customer's pools.
RSM views
View Displays
Physical Devices, including archiving devices, backup devices, and unrelated devices, such as a CD-ROM drive
Locations
● Off-line Media: displays tapes that are part of your archive but are not currently in a device
● Library: displays tapes in a device
Work Queue Tasks in the work queue, including the task status and history. Displays a list of all Archiver tasks
undertaken since the Archiver software last started, to a maximum of 20. This list is automatically
purged after a set number of hours.
Operator Requests from Archiver and other software using RSM, including the request status and history
Requests
When software such as Archiver uses a tape, the software writes a unique
ID in the tape's header so that RSM recognizes it.
● If the tape has no header, RSM assigns the tape to the Unrecognized pool.
This usually means the tape is new, but it can mean the tape has data but its
header is unrecognizable.
To use the tape, move it to the Free pool. If you do not want to use the tape,
eject it.
● If the tape has a recognizable header from software outside this Prinergy
system, RSM assigns the tape to the Import pool.
This usually means the tape is from another Prinergy system or from Windows
NT Backup.
You can move the tape to the Free pool or directly to an application pool. If
you move the tape to an application pool, existing data on the tape is retained.
For example, you could do this for Windows NT Backup tapes.
Column Description
name
Description The physical location where the task is being performed—for example,
a library or specific medium
The following table describes possible column entries in the Work Queue details
pane.
Queued RSM has not yet begun the task. This is the time between when the
request is issued and when RSM starts examining the request.
Failed The task was not completed successfully. To see a description of the
failure, highlight the Failed task.
Waiting The task has stopped and is waiting for an event to happen before it
can continue—for example, a mount request when a drive is already
in use will pause the request until the drive is dismounted.
202 Chapter 15—Archiving
16 Backup
Removable Tracks removable storage media and manages devices and media
Storage
Part of Microsoft Management Console (MMC), which is built into
Manager
the Windows operating system
(RSM)
Backup planning
Develop a backup plan in order to safeguard your data and minimize down
time in the event of an emergency.
Schedule
With third-party software, you can choose how frequently backups occur and
at what time.
Backups with third-party software 205
Data to back up
With Prinergy Online Backup, you do not have to configure the data to back up.
With third-party software, use the following table to determine the Prinergy data
that must be backed up onto media in order to recover your system:
206 Chapter 16—Backup
Location of Essential
data
Database
● The BACKUP_DESTINATION folder on the primary server
● The ZIP_FILES_DESTINATION folder on the primary server
Prinergy and
● Drive that holds Prinergy system files
secondary
servers Important: You must exclude the following folders from all backups, or the backup will negatively
affect the Oracle database and may result in lost production.
If your system has a C:, D:, and E: partition scheme, exclude the following folders:
❐ D:\oracle\oradata
❐ E:\oracle\oradata
If your system has a single C: partition scheme, exclude the following folders:
❐ C:\oracle\oradata
Where to back up
If your third-party software backs up to disk, you must perform one of the
following subsequent steps:
● Save the backup file to media.
● If your company has a corporate backup strategy, make the Prinergy backup
file available on a server so that it is backed up as part of that strategy.
1. Ensure that there is enough tape space available in the tape drive to
store the data that is about to be backed up, and replace the tape if
necessary.
Tip: If your backup software uses Removable Storage Manager, you
can assign additional tapes to the Free pool. RSM can then draw
additional tapes, if they are required.
2. If the Oracle Backup Manager scheduler is running, wait for the backup
to occur.
The scheduler, which starts automatically when Prinergy starts, runs
each night at 11 p.m. to determine the backup requirements and to
schedule the backup to start at the time you specified.
Prinergy Online Backup option 209
Schedule
A backup typically occurs every night at 11 p.m.
The backup occurs while Prinergy is running; the system can continue to be used
as normal. However, if you run a backup while your system is online and
processing jobs, the backup will take longer and Prinergy may process jobs slower.
Prinergy Online Backup automatically checks that the backup was successful.
By default, this check is done eight hours after the backup started; your service
representative can set this to a different time.
Do not change the parameters of Oracle Backup Manager without consulting
your service representative.
210 Chapter 16—Backup
Data to back up
With Prinergy Online Backup, the data that you back up has already been
configured to match your backup plan.
Prinergy Online Backup cannot back up the RAID or non-Prinergy servers. This
means that job data must be archived. Alternately, you can devise a separate
backup plan for backing up job data, independent of the system backup.
c. Ensure that Contains other media pools is selected and then click
OK.
d. Right-click Backup, select Create Media Pool, and type the
following information in the boxes:
Media information box Select Contains media of type, and then specify
the type of media you use:
● 8 mm AIT1
● LTO Ultrium
6. On the Backup tab in the Backup Utility window, define a small backup
job to back up a few test files. In the Backup media or file name list,
select New and then click Start Backup.
7. In If the media is overwritten, use this label to identify the media
box, type the tape name, and then click Start Backup.
This process causes the NT Backup utility to take a tape from the Free
media pool.
8. When the backup is complete, close the Backup utility.
9. In the Computer Management window, locate Storage > Removable
Storage > Media Pools, and move the allocated tape into the Backup
> Prinergy pool.
10. Repeat this process to allocate at least two tapes to the Backup >
Prinergy backup pool.
You can add Prinergy secondary servers, render stations, and the InSite
software Web servers to the list. You cannot add tertiary servers.
1. If possible, find out why the backup failed. Backups may fail for a
number of reasons, including:
● Insufficient media
● Removable storage device not ready
● Cables disconnected between the device and the server
● Network problems
2. If you can identify the cause of the failure, take the appropriate steps
to prevent future failures, if possible.
3. If you can’t identify the cause of the failure or the failure persists,
contact your service representative.
Every-other-day rotation
In this strategy, you allocate two media to back up and rotate them every other
day.
This strategy is the simplest to maintain but provides the least protection, since
there are only two days of backup data available at any given time.
Weekly rotation
In this strategy, you allocate a different medium for each day of the week that
you run a backup. For example, if you run a backup every day of the week, you
must allocate seven media.
This strategy provides one week of backup data and gives you more protection
against data loss than rotating media every other day. However, media
management may be more complex, especially if you are using an individual tape
drive.
Media and devices supported for backup 215
Note: There is no guarantee that the first tape will always be used on a Monday,
the second tape on a Tuesday, and so on. Therefore, you may want to label media
numerically—for example, Tape1, Tape2, and so on—rather than label media by
days of the week.
Bi-weekly rotation
In this strategy you allocate a different media for each day of the week that you
run a backup over a two-week period. For example, if you run a backup every
day of the week, you must allocate 14 media (twice the number of media required
for the weekly media rotation strategy).
This strategy provides two weeks of backup data, giving you additional protection
against data loss. (You may also want to take the previous week’s media off-site
to further safeguard your data.) However, media management may be more
complex, especially if you are using an individual tape drive.
Note: There is no guarantee that the first tape will always be used on a Monday,
the second tape on a Tuesday, and so on. Therefore, you may want to label media
numerically—for example, Tape1, Tape2, and so on—rather than label media by
days of the week.
Media
If you use Prinergy Online Backup, you must use one of the following supported
tape formats:
● DLT (Digital Linear Tape)
● AIT (Advanced Intelligent Tape)
If you use third-party software for backups, you can use any media.
216 Chapter 16—Backup
Devices
You must use a device that has been qualified for Prinergy backups. For a list of
qualified devices, contact your service representative.
In general, there are two types of devices:
● An individual, or stand-alone, tape drive is a removable storage device with
a single tape drive. This type of device requires you to manually insert and
remove tapes.
● A tape library is a removable storage device that contains one or more tape
drives. This type of device automatically loads and unloads tapes.
If you expect the data to span more than one tape, you must use a tape library.
These are guidelines that you can use to keep your Prinergy system running
in optimum condition, minimize down time, and improve system stability.
1. Check the eCentral portal for Prinergy updates and apply them when
appropriate. The eCentral portal is at https://ecentral.kodak.com/.
2. Check fans and air ducts for dust and any other deposits on all systems
and peripherals. If required, hire professionals to clean the systems.
3. If you have Emergency Platemaking or Prinergy Hot Standby installed,
test those procedures.
Next:
There are other measures you can take to free up more disk space, such
as moving the pagefile. However, these are more technically complex
measures and should be executed by your service representative. So if
the above solutions are not sufficient, contact your service representative.
See also:
Compressing the database on page 220
220 Chapter 17—Maintenance
To be The size of all the database tables and indexes that will be
compressed compressed, in GB
Name The name of the internal database object that is currently being
compressed
Item Description
Elapsed time The amount of time it has taken so far to compress the database
object identified in Name
8. Start Prinergy.
9. Start the Prinergy Workshop software.
10. After compressing the database, back up the database using the Oracle
Backup Manager.
Note: The first time that you back up the database after compressing
it, the backup might be slightly slower than usual.
The amount of space that is freed by compressing the database depends on the:
● Size of the database
● Length of time since the last compression
● Number of history entries that have been deleted. You control how frequently
history entries are deleted.
Software updates
Software updates are available on the eCentral portal.
Prinergy software is updated in two ways:
● Updates: minor changes, for example, to fix problems
● Upgrades: major changes that add new features and include all updates
issued since the last upgrade
Check the eCentral portal regularly for software updates. Download the
PUpdate installer files for the software version that is on the server you
want to update.
Note: On the eCentral portal you may also see a command-line utility
available for installing Prinergy software updates, called PPU (Prinergy
Patch Utility). Do not run this utility unless you have problems with the
PUpdate installer file, or you need to remove the installed update.
Minor updates
You must install each minor update sequentially. You cannot skip an update
version—for example, you cannot install version 4.0.2.3 and then version 4.0.2.5.
Tip: The PUpdate utility allows you to install multiple minor updates at once.
Upgrades
For information about upgrading Prinergy software, see the Prinergy Upgrade
Guide, available at https://ecentral.kodak.com/ .
2. On the Downloads page, locate the update that applies to the software
version that is installed on the server you want to update.
3. Click the download file (usually PUpdate.zip) and save it to the
Temp folder on the Prinergy primary server. If there are multiple
download files for the update, save them all to the same folder.
4. Copy the download files to the Temp folder on each secondary server
and render station that you want to update.
Note: You must update Prinergy on the primary server before updating
the secondary servers and render stations.
Note: The upgrade process leaves the old database untouched so that
you can roll back to Prinergy 3.x if necessary. However, afer you delete
the Prinergy 3.x database, you cannot roll back to Prinergy 3.x.
1. When you see a tool tip on the bottom taskbar of the Windows screen
on the Prinergy primary server advising you to delete the Prinergy 3
database, click the tooltip.
A detailed message appears, explaining how and why you should
delete the Prinergy 3 database to free disk space.
2. Read the message, and click Close.
The Delete Prinergy 3 Database menu item appears on the Tools
menu. It is not available until you stop Prinergy.
3. Stop Prinergy.
4. From the Tools menu, select Delete Prinergy 3 Database.
5. In the Delete Prinergy 3 Databasedialog box, review the messages,
and then click Delete Prinergy 3 Database.
6. When the process is complete and the Deletion Status dialog box
displays Succeeded, click Cancel to close the dialog box.
The Oracle 8 software is deleted, along with the Prinergy 3.1 database files, log
files (including archived ones), and backup files (including compressed ones).
It is no longer possible to roll back to Prinergy 3.x. The Delete Prinergy 3
Database menu item is no longer available.
226 Chapter 18—Prinergy updates
19 Large systems
Secondary servers
You cannot share secondary servers between Prinergy systems. When you install
the Prinergy Server software on a secondary server, the secondary server is
associated with a specific primary server and a specific Prinergy system. If you
want to add a secondary server to a different Prinergy system, you must first
remove the secondary server from the original Prinergy system.
See also:
Administering Dashboard on page 169
4. Click OK.
230 Chapter 19—Large systems
20 Glossary
Glossary
action
A request that comes from a client workstation and is processed by the
server.
action detail
Information about a recorded action—for example, the date and time that
the action or process was performed, file names, and the severity of the
information. Recorded actions and action details are displayed in the
history log.
application pool
In the Microsoft Removable Storage Manager (RSM) service, a
user-defined media pool used to designate the data that is written to
specific media. Media that have been used to archive Prinergy jobs belong
to one or more application pools.
Araxi Service
A service started automatically by the operating system when Windows
starts on a Prinergy server. Araxi Service is responsible for starting
daemons and other processes when Prinergy is started. The service can
also monitor and restart processes that it did not start directly (that is,
processes that were started by other processes).
colorant
A pigment, dye, phosphor, or other such substance that produces a color.
Colorants are like building blocks of colors—for example, green is
232 Chapter 20—Glossary
color database
A database that contains information about spot colors—for example,
process color recipes and ink parameters necessary for trapping.
CT file format
A four-color (CMYK) continuous-tone (or contone) raster file format.
Gradient tones and continuous-tone data are sometimes converted to
CT format.
CT/LW
Relating to a raster page that contains CT files, LW files, or both; or to a
workflow that creates CT and LW files.
daemon
A software process on a server that runs behind the scenes to perform
specific tasks. It has no user interface; you do not interact directly with a
daemon. Instead, you can make requests through the client software.
233
destroy
To permanently delete a job and all references to it from the system.
digital master
A PDF file created by Prinergy is a digital master because it is a complete,
reliable entity. Only page description information is contained in the PDF
page. Proofs, films, or plates are made from the same PDF file by selecting
an appropriate output process plan.
dynamic column
A column that appears automatically in a Workshop window or pane
when an element is being processed. The column indicates the process
template used to process the element and the processing status.
element
Any item within a job—including an input file, page, page set, signature,
surface, or separation.
file optimization
The process of checking and optimizing resources in PDF files. It optimizes
the PDF to create a predictable digital master.
file reference
A reference created when an input file or imposition plan is added to a
Prinergy job or Prinergy Evo input file process.
234 Chapter 20—Glossary
home server
The job server for a particular Prinergy job. When you create a job, you
are required to select a job server on which your job will be stored.
hot folder
A folder that is monitored for incoming files as a trigger for an automatic
operation. The software that processes the files checks the folder location
on a regular basis, and automatically processes any files found there.
ICC profile
A color space description that acts as a standard for accurate reproduction
of colors across different platforms, devices, and applications.
image optimization
A reduction of the size of images in the input file by cropping and
downsampling during the refine process.
imposition plan
A file containing an electronic description of the marks, geometry, and
layout of page positions for one or more signatures. An imposition plan
typically does not contain page content.
imposition proof
Imposed content that is output from a proofing device.
job
The basic unit of work in a printing workflow.
job metadata
Information about job data (content).
job ticket
A collection of information related to one or more processing steps that
must be carried out. It includes a map or route that specifies which JTPs
to go to and in what order. It can also include information about which
files to process, processing options, destinations, and imposition plans.
JTP pool
One or more similar JTPs that have been grouped together to further
automate the workflow. A JTP pool lets you direct the software to
automatically distribute tasks to individual JTPs, rather than you having
to coordinate which JTP to use. This helps you automatically process
multiple jobs at the same time.
layering
The ability to assign two or more PDF pages to the same page position
in a page set. Layering is typically used with regional versioning.
236 Chapter 20—Glossary
line work
Data characterized by sharply defined lines and very clear transitions
from one color to another—for example, text. Line work is stored in the
computer as a series of geometric (vector) drawing instructions.
LW file format
A file format that contains line work data. LW files support CMYK only
(no spot colors) and up to 256 colors.
maintenance mode
A system mode that enables you to update Prinergy, while preventing
the software from writing invalid backups. Maintenance mode temporarily
disables Prinergy backups but enables you to continue running jobs.
media pool
A logical group of archive media that is used to organize which data is
archived to which media.
miscellaneous files
Files that are not added to a job on their own, for example, fonts and
images. If these files are stored in the job folder, you can archive them
and retrieve them individually or as part of the job.
normalize
A step in the refining process that creates PDF pages from input files.
The resulting PDF files contain refined pages. Options in the normalize
process are: OPI, image optimization, and font handling.
Orbacus
An implementation of CORBA. It is part of the internal communications
structure.
page position
page set
An ordered set of numbers that identify the pages required for a
publication.
PDF/X
Abbreviation for Portable Document Format eXchange. An exchange
format for sending pages between a page preparation site and a printing
site. PDF/X is a subset of the full PDF specification.
peer-to-peer network
pre-job
A unit of work that stores elements that can be used in one or more jobs,
or that creates a new job from an exported job.
primary server
The main server in a Prinergy system. It coordinates requests from
Prinergy Workshop and maintains the Prinergy database.
printer spread
The pairing of pages as they may occur on a printing press.
process
An action that is controlled by a process template—for example, refine,
output, and archive/retrieve/purge. All other interactions with Prinergy
are referred to as actions. A process requires one or more entities on
which the process will operate (such as input files, PDF pages, signatures,
surfaces, or separations) and a process template that specifies how the
process will operate on the entities.
process template
A file containing options and settings that tell the workflow processor or
the software how to perform a process.
purge
To remove selected job files from the server on which a job is stored after
the job files have been archived. The job remains in the system because
job metadata is retained in the database.
239
reader spread
The pairing of pages in numerical order, as a reader would view them (for
example, 2 paired with 3, 4 paired with 5, and so on).
recorded action
A system activity (including a process) that appears in the history log,
such as adding a file to a job, assigning a page, setting the page geometry,
and initiating the output.
refine
To convert PostScript data into PDF data, optimized for output.
refined page
A PDF file of a page from a refined input file.
render
To determine the output resolution and how Prinergy will handle spot
colors.
render station
A secondary server that is connected to an output device and is running
a high-resolution renderer JTP. It is generally not used to store jobs or
run other types of JTPs; it is reserved for rendering files for output.
renderer
The software component that rasterizes and screens PDF input files.
240 Chapter 20—Glossary
retrieve
To restore archived files. You can retrieve only those job files that have
been previously archived.
run list
In Preps imposition software, the collection of pages that makes up a
signature.
scatter proof
secondary server
A type of server in a Prinergy system. Like the primary server, the
secondary server runs Prinergy Server software but, unlike the primary
server, it does not store the Oracle database. Secondary servers can run
some JTPs to facilitate distributed processing and improve system
performance. A Prinergy system can include multiple secondary servers.
sheet
Both surfaces of one printed press sheet.
signature proof
soft proof
A proof displayed on a computer monitor.
241
software process
A Prinergy Server software component that performs a specific task. You
can monitor the status of Prinergy processes in the Processes window of
Prinergy Administrator.
template
template job
A job that contains settings that you want to use in other jobs. You set
up a template job and use it to create new jobs. Any existing job can act
as a template job.
tertiary server
A Windows 2000 or Windows 2003 server that is connected to the
Prinergy system via the network but does not run any Prinergy software
components. A tertiary server stores job folders and/or input files for
Prinergy jobs.
trapping
A printing technique in which adjacent printed colors are slightly
overlapped to ensure that white space does not appear between the
colors.
user account
An account in a Windows operating system that provides a user with a
unique profile with which to log on to the system and access resources.
vector drawing
The geometric system used to define lines and curves in computer
graphics. It is most often used for line drawings.
242 Chapter 20—Glossary
workflow template
A file that links several process templates together to give more
automation.
workgroup
A collection of computers that share resources such as data and devices.
A workgroup does not have a dedicated server or hierarchy among
computers. May also be referred to as a peer-to-peer network.
Index
A O
Archive/Retrieve JTP 26 Optimize JTP 27
Oracle Backup Manager 208
C
P
CEPSConverversion JTP 26
Color Matcher JTP 26 permissions 149
Copydot JTP 26 PostScript Level 3 JTP 27
CTLWOutput JTP 26 Primesetter JTP 27
Print Console JTP 27
PrintLink JTP 27
D Proofing Device (256 MB) JTP 28
Disk Purge JTP 26 Proofing Device (512 MB) JTP 28
Domain Name System 121
DOP JTP 27 Q
Quarsar JTP 27
E
Expose JTP 27 R
Rules-Based Automation
G user rights 149
Generate JTP 27
Generic JTP 27 S
SFMHOSTS file 121
H Signasetter JTP 27
Heidelberg Herkules JTP 27 Signature ID Codes 156
Heidelberg Primesetter JTP 27 Software updates 223
Heidelberg Quasar JTP 27 Speedway Engine Manager JTP 28
Heidelberg Signasetter JTP 27
Herkules JTP 27 T
Topsetter Engine Manager JTP 28
I Trap JTP 28
Import/Export JTP 27
U
N Updating software 223
Normalize JTP 27 user rights 149
V
VectorOutput JTP 28
Eastman Kodak Company
343 State Street
Rochester, NY 14650 U.S.A.
© Kodak, 2008. All Rights Reserved.
TM: Kodak
To learn more about solutions from Kodak, visit
http://graphics.kodak.com.
Subject to technical change without notice.