Você está na página 1de 254

Prinergy

Workflow System
Version 5.0

System Administration Guide


English

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/

Internal 731-00463C-EN Rev J


Revised 2008-12-03
Contents
1 Getting started 1
Configuring Prinergy after installation......................................................................................................................................1
Starting Prinergy.............................................................................................................................................................................1
Stopping Prinergy...........................................................................................................................................................................2

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

7 Mac client computer protocols 107


Qualified tertiary servers and Mac client computer file-sharing protocols.............................................................107
List of Mac client computer file-sharing protocols and related software.................................................................110
Limitations of Mac client computer file-sharing protocols............................................................................................111
Understanding file resources................................................................................................................................................112
Contents vii

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

8 Proofing devices 137


Setting up a Kodak proofing device....................................................................................................................................137
Adding a Kodak proofing device................................................................................................................................137
Configuring a proofing device....................................................................................................................................138
Setting up a third-party proofing device...........................................................................................................................139
Supported third-party proofing devices..................................................................................................................139
Determining if a third-party proofing device can be used with Prinergy........................................................140
Configuring a proofing device....................................................................................................................................142

9 Adding output devices 145

10 Digital printers 147


Adding a digital printer..........................................................................................................................................................147
Changing a digital printer's file transfer protocol...........................................................................................................147
Removing a digital printer....................................................................................................................................................148

11 RBA setup 149


Controlling who can use RBA..............................................................................................................................................149
Setting up e-mail service for RBA.......................................................................................................................................150
Handling rejected RBA e-mail messages...........................................................................................................................151
Preparing for RBA e-mail if you use InSite Prepress Portal..........................................................................................152
Setting up file transfers for RBA..........................................................................................................................................153
Enabling client computers to use RBA..............................................................................................................................154

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

14 Database reports 177


Running built-in reports.........................................................................................................................................................177
Built-in reports.........................................................................................................................................................................178
Creating custom reports.......................................................................................................................................................180
Viewing database documentation......................................................................................................................................182
Interpreting history numbers...............................................................................................................................................183
Character data in the database...........................................................................................................................................184

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

Configuring backups with Prinergy Online Backup................................................................................................211


Performing a backup with Prinergy Online Backup..............................................................................................212
Monitoring database backups....................................................................................................................................213
What to do if a backup fails.................................................................................................................................................214
Media rotation strategies.....................................................................................................................................................214
Media and devices supported for backup........................................................................................................................215

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

18 Prinergy updates 223


Software updates...................................................................................................................................................................223
Updating Prinergy software.................................................................................................................................................223
Deleting the Prinergy 3.x database...................................................................................................................................224

19 Large systems 227


Multiple Prinergy systems...................................................................................................................................................227
Prinergy across a WAN........................................................................................................................................................227
Connecting to Administrator on another server............................................................................................................229

20 Glossary 231
x Prinergy
1 Getting started

Basic information that you need when you install Prinergy® for the first
time.

Configuring Prinergy after installation


After your Prinergy system is first installed, you need to configure several
aspects of the system, such as servers, user rights, and so on.
Requirements:
Prinergy must be installed.

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.

1. From the File menu, select Start Prinergy.


2. If you have more than one Prinergy server, in the Start Prinergy dialog
box, perform one of the following actions:
● To start Prinergy on all Prinergy servers in the Prinergy system,
select All Servers.
● To start Prinergy on the most recently selected server(s), select
Selected Server.
Tip: To simultaneously select multiple servers, hold down the Shift
key and click the server names.
2 Chapter 1—Getting started

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.

1. From the File menu, select Stop Prinergy.


2. If you have more than one Prinergy server, in the Stop Prinergy dialog
box, perform one of the following actions:
● To stop Prinergy on all Prinergy servers in the Prinergy system,
select All Servers.
● To stop Prinergy on the most recently selected server(s), select
Selected Server.

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.

Prinergy product family


The Prinergy product family includes:
● Prinergy Connect: a full-featured Prinergy system for commercial and
publications printers who need page processing, imposition, and film-making
or platemaking.
● Prinergy Powerpack: a Prinergy system designed for offset, flexographic, and
gravure packaging printers.
Products that are related to the Prinergy family include:
● Kodak InSite: a Web portal that lets you (the printer) and your customers
(print buyers) work with print jobs over the Internet.
● Kodak Link: software that automates the exchange of production data between
a prepress workflow system and a Management Information System (MIS).
● Kodak Preps: imposition software for the commercial printing industry.

Software components
Prinergy is a client/server system that includes the Workshop client
software and several server software components.

Client software, Workshop


Prinergy Workshop is the main client software in a Prinergy system. It is the main
way that you interact with the Prinergy system by creating jobs, triggering
processes, and so on.
4 Chapter 2—System overview

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

Daemons (multiple) Execute processing that is unrelated to PDF files—for


example, job ticket creation, job status and history,
imposition, and input file registration

Araxi Service Launches core processes when the server starts


(Araxi.exe )

These components are installed only on the primary server:

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

Prinergy Archiver Archives Prinergy jobs (includes archive-related JTPs and


Windows RSM)

Prinergy Backup Backs up the database to disk


Software components 5

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.

How the client and server interact


Each time that you perform an action on a job in Prinergy Workshop:
1. Workshop asks Prinergy Server to perform the action—for example, to
normalize PostScript® input files.
2. Prinergy Server creates a job ticket for the requested action.
3. For each step in the job ticket:
a. Prinergy Server software sends the job ticket to the JTP on the appropriate
server.
b. The JTP performs the steps defined in the job ticket.
c. The JTP reports back to Prinergy Server software.

4. When the action is complete, Prinergy Server software updates Workshop


and the database to reflect the current status of the job and related files,
including any new system files in the job folder.
6 Chapter 2—System overview

Architecture
Prinergy uses PDF as the internal file format, tracks tasks with job tickets,
and distributes tasks to job ticket processors.

PDF as the internal file format


The internal file format in Prinergy is PDF. This means that all input files of all
file types are converted, or “normalized,” into PDF digital masters for use in
subsequent phases of the workflow.
PDF files:
● RIP reliably and predictably
Unlike Adobe PostScript files, PDF files do not have to be interpreted to ensure
that all referenced resources, for example, fonts and images, are available.
Thus, rasterizing—the second phase of RIPing that occurs just before
output—is a straightforward and predictable process.
● Are independent of any platform, operating system, authoring software, and
output device
● Are viewable in Microsoft® Windows, Apple Mac OS, and UNIX® operating
system software
● Are printable to output devices at high resolutions
Although Prinergy uses PDF internally, it uses many other file formats for input
and output. For example:
● It accepts several file formats as input files, including PostScript, EPS
(Encapsulated PostScript), and many others.
● It produces several file formats as output, including vector or raster formats.
For a list of supported file formats, see Workshop Help.

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

Job ticket processors (JTPs)


A job ticket processor (JTP) is a software process that performs a specific step
to help process a job ticket.
Prinergy has a JTP for each possible kind of processing—for example, refine,
output, and archive JTPs. Some processes, such as refine, require several JTPs
strung together.
You can have multiple instances of the same type of JTP running on a server. For
example, with multiple instances of the Normalizer JTP, you can process multiple
jobs simultaneously. For further performance enhancement, you can distribute
instances of the same type of JTP on different servers, and you can create JTP
pools.
In Prinergy, a job ticket includes a map that specifies which JTPs to use and in
what order.

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

Type of server Description/purpose Server software Operating system Stores


installed jobs?

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

Render station A secondary server that runs Windows 2000 Server No


high-resolution rendering or Windows 2003
software and is connected to an Server
output device

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

Component Description Location

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

Input files Customer files that contain the original Either:


information for a printing job, such as
PostScript files or imposition plans
● UserDefinedFolders folder in the job folder
● Any computer that is visible from the job’s home
server, such as a file server

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.

Distributing the system


Prinergy is an expandable system with a built-in ability to distribute jobs
and processing work across multiple servers.
If you have multiple servers, you can distribute Prinergy components
throughout your system to increase overall performance. Although
Prinergy can work well as a single-server system, too much simultaneous
demand can overwhelm any system.

Distributing JTPs across servers


You can distribute JTPs over multiple servers for optimal load sharing and
increased throughput. To distribute JTPs, you can:
● Place different types of JTPs on different servers—for example, place archiving
JTPs on one server and other types of JTPs on another server
● Place the same types of JTPs on multiple servers—for example, place the
Normalizer JTP on two servers
The best JTPs to distribute onto secondary servers are CPU-intensive tasks, such
as rendering final output.
Note: Some daemons also run on multiple servers, but are completely controlled
by the Prinergy system. You cannot control which server daemons run on.
10 Chapter 2—System overview

Distributing jobs across servers


You can distribute jobs onto primary, secondary, or tertiary servers. (You cannot
store jobs on file servers.)
The server where a job is stored is called the “job home.”
It is best to distribute jobs only on secondary and tertiary servers, not on the
primary server. By reserving the primary server for software, you increase
performance on the primary server.

Distributing input files across servers


Input files can be stored on any server, including file servers. You are not forced
to store them in the job folder on the job’s home server.

Web browser access


Documentation and some software components are available through a
web browser over HTTP.
Note: If your system has a firewall, you may need to open the ports listed
below.
In the following URLs, replace server with the name of your Prinergy
primary server.

Documentation
Documentation URL and port

RBA Reference http://server:61235/en/AutoDoc/Index.html

Administrator Help http://server:8082/help/

Connect Workshop Help http://server:8083/help/

Powerpack Workshop Help http://server:8084/help/

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

InSite http://server/Site/Pages/login.aspx 80, unless InSite is using SSL, operates in a DMZ,


or requires other specific configurations

Dashboard http://server:80/Dashboard 80, unless 80 is used, in which case Dashboard


uses 51234

Installation folder (%AraxiHome%)


The installation folder for Prinergy software is identified by an environment
variable called %AraxiHome%.

%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:

Situation Default installation folder

New installation with Windows 2003 C:\Prinergy

New installation with Windows 2000 D:\Prinergy

Upgraded version that has not been rehosted D:\Prinergy 2.0.4


12 Chapter 2—System overview
3 Licenses

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.

Adding new licenses


If you want to enable new options on your Prinergy system, contact your customer
service representative and purchase a new license key.
When you get a new license, remove the current license key and enter the new
license key with the additional features. If you do not remove the old license, the
Prinergy system might not recognize the new license.
With some licensed features, such as screening options in output JTPs, you must
manually enable the license before the feature can be used, even though the
14 Chapter 3—Licenses

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.

Temporary license keys


You can obtain temporary licenses for particular features in order to run features
on a trial basis. For example, you can get a license key to temporarily add a
CEPSConversion JTP to your system and test it with your workflow. After a
predetermined date, the license expires and the feature is disabled.
Enter a temporary license key in the same manner as a permanent license key.
Once you enter a temporary license key, the license key itself does not appear
in Prinergy Administrator again. However, any related features appear in the
features list when you view licensed options, and the Expiration column indicates
when the feature will expire.
Prinergy monitors licenses on a regular basis and issues a warning when a
temporary license is about to expire.
If you want to permanently license a temporary feature, contact your service
representative to obtain a new permanent license key.
Note: You cannot have more than one permanent license key because the
pemanent license key includes all the features you have purchased. You can have
multiple temporary license keys, each enabling a feature you want to test.

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

Included Included in the base Creosettes Not applicable.


Prinergy license.

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

Type Description Screens of This Type How It Is Enforced


®
Staccato At resolutions of 1440 dpi Staccato-10, You can select unlicensed screens in a
screen and lower, no license is Staccato-20, and process template, but the process fails.
licensing required. At resolutions Staccato-25 screens
higher than 1440 dpi, a
license is required.


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

or used to create impositions for Prinergy. The material


and status type information that is automatically
gathered by Business Link during the production
process can be sent to an MIS, allowing automated
tracking of materials and seamless distribution of status
information from Prinergy and Insite in the MIS.

Clients Additional Prinergy client licenses are available


individually or in 5-packs.
ColorMatching Enables ICC profile-based proofing and final output.
on Output
CT/LW & Enables output to Brisque® CT/LW & TIFF/IT formats.
TIFF/IT Output
Custom Enables you to create custom reports by connecting
Database the database to third-party reporting software, such
Reporting as Business Objects™ Crystal Reports®.
Dashboard Increase the number of your Dashboard clients. (The
first Dashboard client is free and does not require a
license.)
Dashboard is a distributed browser-based interface for
providing status and progress in production. It provides
prepress management and customer service
representatives better visibility into the production
process with an overall view of job status across single
or multiple Prinergy workflow systems throughout an
operation.
Digital Blueline Cuts and collates (de-imposes) the pages from an
Proofing imposed flat and sends the pages to a printer in reader
(Signature order.
Booklet)
EPM and Job EPM (Emergency Plate Making) enables you to process
Replication jobs and produce plates on a secondary server if a
primary server fails, but does not allow you to see
existing jobs.
Hot Standby (EPM+) allows a customer to continue
using Prinergy with minimal downtime by running the
database server on the secondary server without losing
job data.
Job Replication duplicates your job information on a
second tertiary server and enables you to access job
files in the event that your tertiary server fails.
Output Additional output engines for low or high resolution.
Prinergy options 17

Packaging Enables automation of packaging layout creation. It


Layout enables Prinergy to automatically take job information
Automation from your management information system (MIS) and
create a layout designed for your printing environment.
Prinergy Layout Automation validates the information
and allows the layout to be manually edited with an
easy-to-use editing tool; you do not need to start Kodak
Pandora® step-and-repeat software. Prinergy
Rules-Based Automation is a prerequisite.
PDF Batch This Acrobat® plugin provides the ability to
Trapping automatically trap PDF pages during a Prinergy refine
process (includes advanced features, such as enhanced
trap corner geometry settings and keepaway traps for
packaging related work).
PDF Compare This Acrobat plugin provides the ability to analyze two
PDF files, with the differences being summarized in a
new PDF file that can be saved or emailed to clients.
Using Acrobat layers, the common elements are
segmented from the change elements for easy
inspection.
PDF File Editor This Acrobat plugin enables you to edit refined PDF
files using Adobe Illustrator®.
PDF Merge This Acrobat plugin assists in correction cycles. It
enables you to compare two PDF files, preserve objects
from one file, and apply those objects to the other file.
For example, you can apply changed objects from a
corrected file to the trapped original while maintaining
the traps.
PDF This Acrobat plugin enables you to add white, bump,
Platebuilder and varnish plates to refined PDF files, and gives you
an automatic mechanism to create varnish and white
separations for appropriate portions of graphics.
PDF Trap This Acrobat plugin enables you to trap objects and
Editor pages, set trap geometry, and create keepaway traps.
PrintLink Ink Dramatically reduces make-ready time by generating
Key Setting digital ink profiles and routing them to the press
interface. It automatically communicates precise ink
coverage information and print form geometry from
prepress to the pressroom for digital ink-key presets.
This approach reduces time, paper, and ink wasted in
adjusting ink keys on the press. PrintLink also eliminates
the time spent scanning imaged plates and maintaining
a plate scanner.
18 Chapter 3—Licenses

Production Automatically gathers information regarding the


Reporting production of jobs from Kodak Prinergy and InSite. The
data can then be sent to the MIS in tab-delimited
format for job costing or used to create stand-alone
reports describing prepress activity and materials used
in jobs.
Rules-Based Allows you to create automatic rules for any existing
Automation manual event, business process, or daily step in your
(RBA) printing production workflow. Rules-Based Automation
includes sample rule sets, but more importantly, it
allows you to create custom rules unique to your
business. As a result, you can organize all stages of
print production, enabling your business to run more
efficiently.
Refine Additional refine engines.
Regional Allows multiple page assignments per page set position.
Versioning Layered PDF Versioning uses different layers from
(Layered PDF within a layered PDF to generate different versions
Versioning) within a Prinergy job.
Secondary Allows you to run distributed processes on a secondary
Server server in your Prinergy system.
Distribution
License
Screening Additional screens available--for example, HyperFlex
(screens that allow for smaller dots and/or graphic
elements to be held on plate during UV exposure),
Maxtone (hybrid AM and FM screening is useful for
flexo packaging and other applications where scum
dots are a problem), Seamless (screens that allow
seamless alignment of images across the boundaries
of the artwork for imaging on a cylinder), and Staccato
(stochastic or FM--frequency modulated--screens).
Web Growth Provides linear and non-linear distortion of individual
Compensation plate separations to compensate for paper stretch in
web press operations greater than 37 inches wide.
Viewing licensed options 19

Viewing licensed options


Use this procedure to view your licenses, including what options are
licensed and their expiry dates.

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

The number of instances of the option that you are licensed


Instances column to use. For example, here is where you can see how many
Refine JTPs you are entitled to run on your system.

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.

Selecting a core dongle for Prinergy


If you have more than one dongle installed, you must select one dongle
to be the core dongle.
Requirements:
Stop Prinergy on all servers in the system.

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

Entering a license key


Add a new license to start using the feature that you purchased.
Requirements:
Stop Prinergy on all servers in the system.

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.

Manually enabling a license key


Some licensed features must be manually enabled before they can be
used.
You must manually enable some licensed features before the feature can
be used, even though the feature may be listed in the Prinergy Licensed
Information dialog box. For example, JTP features such as screening
Saving license key information 21

options in output JTPs must be enabled manually. These features are


enabled on a JTP-by-JTP basis.

1. On the primary Prinergy server, in the right pane of the Prinergy


Administrator main window, select the JTPs tab, if it is not already
selected.
For example, if you purchase a license for a new type of screening,
configure an output device JTP such as the Proofing Device (512 MB)
type of JTP.
Note: Select a JTP, rather than a JTP pool. The Type column in the
right pane indicates which items in the list are JTP pools, and JTPs
have an entry in the Server column, while JTP pools do not.

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.

Saving license key information


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.
Requirements:
Stop 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 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.

Removing a license key


Before adding a new license key, remove the old license or the Prinergy
system might not recognize the new license.
Requirements:
Stop 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

Removing a license key


Before adding a new license key, remove the old license or the Prinergy
system might not recognize the new license.
Requirements:
Stop 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.

Inserting a dongle
Insert a dongle into a port on the Prinergy server.

1. Insert the new dongle into a port on the Prinergy server.


Depending on whether the dongle is a parallel or USB dongle, ensure
you insert it into a parallel or USB port.
2. If this is a replacement dongle, return the old dongle to Kodak.

Entering a license key


Add a new license to start using the feature that you purchased.
Requirements:
Stop Prinergy on all servers in the system.

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

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.

Selecting a core dongle for Prinergy


If you have more than one dongle installed, you must select one dongle
to be the core dongle.
Requirements:
Stop Prinergy on all servers in the system.

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.

Starting and stopping JTPs


All JTPs start automatically when Prinergy starts. If a JTP has a problem starting,
Prinergy tries to start it three times and then displays an error message about
the failed JTP. In that situation, you need to manually start the JTP.
Similarly, if a JTP stops responding, you can stop and restart it. Stopping a JTP
does not remove the JTP from the server.

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

Writes whole jobs or individual files onto archiving media.


Archive/Retrieve Locates archived jobs or files on archiving media and returns Archive
the jobs or files to the job server.

Converts CT/LW and TIFF/IT P1 pages to composite PDF 1.3


CEPSConversion Refine
output

Color Matcher Generates data for color-matching proofs to final output Refine

Refine and
Copydot Optimizes copydot files for output
Output

Copies jobs and pre-jobs to create new jobs and pre-jobs on


CopyJob CopyJob
your Prinergy system

Outputs loose pages to the continuous tone/line work


(CT/LW) format for processing and printing in the Kodak
CTLWOutput Output
Brisque workflow system, and for processing in the Prinergy
system for output on a Karat digital press.

Disk Purge Removes selected jobs or files from the job server Archive
Types of JTPs 27

Icon JTP Type Description Group

Perform minor tasks, such as generating thumbnails. The


Generic JTPs Prinergy system manages distribution of these JTPs; you Generic
cannot configure them with Prinergy Administrator.

Generates a layered PDF 1.5 file from a group of refined PDF


Generate 1.3 files. Used by the Kodak Prinergy Layered PDF Versioning Generate
system.

Sends data to a Digital Offset Printer (DOP) such as a


DOP Heidelberg® Speedmaster® 74 DI. Output
This JTP is not related to the Digital Print feature of Prinergy.

Sends data to the Kodak Xpo™ software, which is an interface


Expose Output
to devices such as the Lotem® 400 Quantum® platesetter

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

Exports all or part of a job to a compressed file for import into


another Prinergy system. Also imports imposition plans,
Import/Export populated job tickets (imposition plans with job pages already Import/export
assigned to page positions), and compressed files exported
from the Kodak Page Assigner software.

Converts PostScript language files to PDF, and performs font


Normalize Refine
management and font handling

Optimizes PDF files into digital masters that are suitable for
Optimize print and checks conditions such as compression and Refine
downsampling

Enables Prinergy to output jobs and files in the PostScript 3


PostScript Level 3 Output
file format

Sends data to a number of Kodak and Heidelberg output


Print Console Output
devices, such as the Kodak Trendsetter® platesetter

PrintLink Generates PPF (CIP3) files for digital ink key preset systems Output
28 Chapter 4—JTPs

Icon JTP Type Description Group

Proofing Device Create low-resolutionproofing Devices (256 MB) output that


Output
(256 MB) is suitable for proofing

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

Trap (specific JTPs


Perform trapping in Prinergy Refine
may vary)

Enables output of Prinergy pages in DCS-2, separated


VectorOutput Output
PostScript language, or PDF format

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

Icon Graphical indicator of the type of JTP or JTP pool

JTP
Name User-defined name or generic name for the JTP or JTP pool

Which server the JTP is active on


Server This field is left blank for JTP pool entries, because the JTPs in the
pool can reside on multiple servers.
Starting or stopping a JTP 29

Column Describes

Type Type of JTP or JTP pool

Status of the JTP or JTP pool


● Starting: It is in the process of being added to the server.

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.

Tip: To access the JTP configuration commands, right-click in the JTP


window.

See also:
Types of JTPs on page 26
JTP pools on page 36

Starting or stopping a JTP


Start or stop a JTP and view a JTP's status on the JTPs tab.

1. In the right pane, click the JTPs tab.


2. Perform any of the following actions:
● If the JTP is in Stopped (offline) status, right-click it, and select
Start JTP.
● If the JTP is in Ready status, right-click it, and select Stop JTP.
● If the JTP is in Starting or Stopping status and the status does not
change for at least two minutes, right-click it, and select Stop JTP
Now. When a confirmation message appears, click OK.

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

● Bridge - Delta Technology


● Copydot
● CTLWOutput
● DOP
● Expose
● Heidelberg Herkules
● Heidelberg Primesetter
● Heidelberg Quasar
Output ● Heidelberg Signasetter
● PostScript Level 3
● Print Console
● PrintLink
● Proofing Device (256 MB)
● Proofing Device (512 MB)
● Speedway Engine Manager
● Topsetter Engine Manager
● VectorOutput

● 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

Note: Regardless of whether you add a Copydot JTP under refine or


output, you can use the Copydot JTP in both output and refine process
templates.

3. In the Name box, type a name for the new JTP.


Note: You cannot change the name of the PrintLink, Archive/Retrieve,
or Disk Purge JTP.
Tip: To help you easily identify the JTPs in your system, include the
following information:
● JTP type--for example, Normalize
● Location or server--for example, ServerA
● Other unique identifiers--for example, the options selected for the
JTP. This will help you select only JTPs with the same options when
adding JTPs to a pool.

Example JTP names: Normalize ServerA, Normalize Server

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

● Import Unpopulated Job Ticket to import a blank


imposition plan with blank pages assigned to page
positions
● Import Populated Job Ticket to import an imposition
plan with job pages already assigned to page positions
● Import Job File to import a compressed file containing
Import/export
all or part of a job that was exported from another
Prinergy system
● Export to export all or part of a job to a compressed file
for use in another Prinergy system
● Import Pageset to import a compressed file that was
exported from the Page Assigner

● Refine Copydot Improvements to detect copydot files


and optimize them for use in Prinergy. Always select this
option.
● Descreen/Resample Copydot to descreen and resample
Copydot
copydot files to the output resolution specified in a
process template
● Calibrate Copydot to control dot gain calibration by
selecting a calibration curve in a process template

● 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

For this type of


Select
JTP

If you have a site license for PrintLink, select the Printlink:


PrintLink
Site check box.

● 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.

1. In the right pane, click the JTPs tab.


2. In the list of JTPs, select the JTP that you want to remove.
3. From the JTP menu, select Remove JTP.
4. Click OK when prompted to permanently remove the selected JTP
from the server.

JTP distribution guidelines


When distributing JTPs, consider each server's capacity and the size of
the entire Prinergy system. Avoid adding too many resource-intensive
JTPs on one server--overloading your servers can resullt in system failure.
Before redistributing your JTPs or adding additional JTPs in your system,
read these guidelines.
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 additional instances of exisiting JTPs.
JTP distribution guidelines 35

General JTP guidelines


● For larger multi-server Prinergy systems (systems with more than one
secondary server), you need to offload some JTPs from the primary server
to make resources available for the Oracle database software and jobs.
● For very large Prinergy systems (systems with more than three secondary
servers), consider removing all JTPs from the primary server.
● If job replication is used, only Archiver and Purge--no other JTPs--should run
on the job home server (tertiary) that is being replicated.

JTP guidelines based on server size


The following JTP guidelines list the most resource-intensive JTPs (including
disk, memory, and CPU). Although not listed here, other JTPs that are less
resource-intensive may be installed on the same server.

Recommended JTP setup on a Performance server


Because the Performance server has limited resources, it is generally best to
configure only one of each required type of JTP.

Recommended JTP setup on a Premium server with 4 logical


CPUs
For a premium server that is configured with four logical CPUs (that is, two
hyperthread or dual-core CPUs, such as the PE2600, PE2800, or PE2900 Gen
II), the following JTP setup is a recommended mix of disk-intensive and
CPU-intensive JTPs that avoids saturation of server resources:
● 2 Normalizer
● 2 Optimizers
● 2 Color Managers
● 1 Trap
● 1 Import/Export
● 2 Proof JTPs (or 1 Proof, 1 Print Console)
Note: To avoid server resource saturation, a good general rule is to never install
more than two JTPs of the same type on one 4-CPU Premium server.

Recommended JTP setup on a Premium server with 8 logical


CPUs
For a premium server that is configured with eight logical CPUs (that is, two
quad-core CPUs, such as the PE 2900 Gen III), you can expand the guidelines
for the 4-CPU server to allow up to three of the CPU-intensive output JTPs (for
example, Proof256, Proof512, Print Console) on the Premium server.
Generally, three refine JTPs of the same type (for example, Normalizers) are not
recommended for the Premium server with 8 logical CPUs because although
36 Chapter 4—JTPs

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.

What JTP pools can include


A JTP pool can include JTPs on one or more servers. For example, a pool can
consist of three Normalize JTPs on three different Prinergy servers.
A JTP pool should include only JTPs for which the same features have been
selected. For example, all JTPs in the same Color Matcher pool must have the
same color management feature selected, either Color Management: color
mapping or Color Management: advanced.
A JTP pool cannot include different types of JTPs. For example, you cannot have
an archive JTP in the same pool as a refine JTP.
Creating a JTP pool 37

Creating a JTP pool


Create a pool so that Prinergy automatically distributes tasks to individual
JTPs and, therefore, automatically process multiple jobs at the same time.
Important: All JTPs in a pool must have the same features selected.

1. From the JTP menu, select Create JTP Pool, and then select a pool
type.
Type Description

CEPSConversion Converts Brisque CT/LW and TIFF/IT P1 pages to


composite PDF 1.3 output

Color Match Generates data for color-matching proofs to final output

Copydot Optimizes copydot files for output

Vector Output Creates output in a vector DCS format

Import/Export Exports all or part of a job to a compressed file for import


into another Prinergy system. Also imports imposition plans,
populated job tickets (imposition plans with job pages
already assigned to page positions), and compressed files
exported from Page Assigner.

Normalize Converts PostScript language files to PDF and performs


font management and font handling

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

Proofing Device Creates low-resolution output that is suitable for proofing


(256MB)

Proofing Device Creates high-resolution output that is suitable for proofing


(512MB)

Trap Performs trapping in Prinergy

2. In the Name box, type a name for the JTP pool.


Tip: Give a JTP pool a unique name. To help you easily identify JTP
pools in your system, including the following information:
● Pool type--for example, Color Match
● The word "Pool"
● Number of JTPs in the pool--for example, 3
● Other unique identifiers--for example, include "No Primary" to
indicate that a pool does not include any JTPs on the Prinergy
primary server
Example JTP pool names: Color Match Pool 3, Trap Pool No Primary
3. In the Selected JTPs in the pool box, select the JTPs you want to
include in this pool.
Important: All JTPs in a pool must have the same features selected.
4. Click OK.

Changing an existing JTP pool


With an existing JTP pool, you can add new JTPs to the pool, remove JTPs
you no longer need, or completely delete the pool.

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

2. Perform any of the following actions:


To do this Do this

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

Important: A JTP pool cannot include different types of JTPs. For


example, you cannot have an archive JTP in the same pool as a refine
JTP. In addition, all JTPs in a pool must have the same features selected.
If you remove a pool, the associated JTPs remain on the Prinergy
servers.
3. Click OK.

Types of JTP pools


JTPs can be grouped into several types of JTP pools.
Icon JTP Pool Type Description

CEPSConversion Converts Brisque CT/LW and TIFF/IT P1 pages to composite PDF 1.3 output

Color Match Generates data for color-matching proofs to final output

Copydot Optimizes copydot files for 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.

Converts PostScript language files to PDF and performs font management


Normalize
and font handling
40 Chapter 4—JTPs

Icon JTP Pool Type Description

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

Trap Performs trapping in Prinergy

Vector Output Creates output in vector DCS format


5 Users

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 user accounts


Set up a separate user account for each user in the Prinergy system, so that you
can:
● Provide users with unique profiles and personalized preferences, such as the
position and size of windows in the Workshop software
● Integrate security with the Windows operating system
● Control user rights for individual users
● Use the history log to track the operations that each user performs

About user groups


We recommend that you set up at least two user groups:
● A Users group for people who use only the Prinergy Workshop software
● An Administrators group for people who also use the Prinergy Administrator
software

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

● Do not contain common words, words from a dictionary, or slang in common


usage
● Are complex but relatively easy to remember
● Are kept private. If a password is shared or discovered, change it immediately.
● Are changed regularly, such as every 90 days

Configuring users in a domain


If the Prinergy system is in a domain, use the Active Directory software
on the domain controller to set up user accounts and user groups.

1. On a domain controller, log on as a domain administrator.


2. From the Start menu, select Programs > Administrative Tools >
Active Directory Users and Computers.
3. On the Tree tab, click the domain node to expand the tree.
4. (Optional) Create a group:
a. In the Active Directory Users and Computers left pane, right-click
Users or the folder where you want to create the group, and select
New Group.
b. In the group name box, type a descriptive name for the group, and
select New Group.
c. In the Group scope box, select Global.
d. In the Group type box, select Security.
e. Click OK.
5. Create a new user:
a. Right-click Users or the folder where you want to create the
account, and select New User.
b. Follow the prompts.
User names must:
● Be unique in the system
● Be a maximum of 20 characters
● Include uppercase and lowercase letters
● Exclude these characters: / \ [ ] : ; | = , + * ? < >

c. Select the User must change password at next logon check box,
and click OK.
Configuring users in a workgroup 43

6. Add users to a group:


a. In the Active Directory Users and Computers left pane, right-click
Users or the folder that you created for the group.
b. In the right pane, right-click the group and select Properties.
c. Click the Members tab.
d. Click the Add button. In the Look in box, select Domain. From the
Name column, select the user accounts that you want to add to
the group, and click Add.
To select multiple accounts, hold down the CTRL key.
e. Click OK.

Configuring users in a workgroup


If the Prinergy system is in a workgroup, use Computer Management in
the Windows operating system to set up user accounts and user groups.

1. Log on to the Prinergy system as an administrator.


2. From the Start menu, select Programs > Administrative Tools >
Computer Management.
3. On the Tree tab, click Local Users and Groups to expand the tree.
4. (Optional) Create a group:
a. Right-click Groups and select New Group.
b. Type a Group Name.
c. If you want, type a Description and click Add to add members to
this group.
d. Click Create, and click Close.
5. Create a new user:
a. Right-click Users, and select New User.
b. Follow the prompts.
User names must:
● Be unique in the system
● Be a maximum of 20 characters
● Include uppercase and lowercase letters
● Exclude these characters: / \ [ ] : ; | = , + * ? < >

c. Select the User must change password at next logon check box,
and click OK.
44 Chapter 5—Users

6. Add users to a group:


a. Right-click Users or the folder that you created for the group.
b. In the right pane, right-click the group and select Properties.
c. Click the Add button. From the Name column, select the user
accounts that you want to add to the group, and click Add.
To select multiple accounts, hold down the CTRL key.
d. Click OK.

Setting user rights


Change the default user rights to prevent all users from changing advanced
features, such as creating process templates, changing custom fields, or
deleting history entries.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the User Rights tab.
3. (Optional) If the user does not appear in the Users list, click Add User,
type the person's Windows operating system user name, and click
OK.
4. Set the rights for a user:
a. In the Users list, select the user.
To affect all users, select EVERYONE.
b. In the Rights for list, select the check box next to each right that
you want the user to have.
The following user rights are available:

Destroy history entries.


Delete
History Without this right, an [x] appears next to Destroy History Entries
on the Tools menu in all windows in Workshop.

Destroy jobs in Job Finder.


Destroy
Job Without this right, the user cannot destroy a job. If the user tries to
destroy a job, an error message appears.
Setting user rights 45

Create, edit, and delete process templates and workflow templates.


Temporarily edit process templates from the Start Process dialog
Edit box.
Process Without this right, an [x] appears next to Process Template Editor
Templates on the Tools menu of all windows. An [x] appears next to Edit,
Rename, and Delete when you right-click a process template or
workflow template in the Process Templates pane.

Lock Lock preflight profiles to restrict editing by users.


Preflight Without this right, the Locked option is disabled on the Preflight
Profiles Profile Manager dialog box, allowing users to edit preflight profiles.

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.

Create, edit, delete, enable, disable, move, import, or export rule


sets for Rules-Based Automation in Workshop. Editing includes the
ability to add a description to a rule set. Without this right, the Rule
Set Manager window and the Rule Builder window appear in
read-only mode. This right does not affect a user's ability to start or
view information about rule sets, including viewing all of the rule
Manage
sets in Rule Set Manager, viewing the content of a rule set in Rule
Rule Sets
Builder, viewing the Rule Set Info dialog box that describes a rule
set, viewing the RBA Status Web pages, and viewing the RBA
Reference Web pages. If you use Prinergy Rules-Based Automation,
do not give all users the right to work with rule sets. In other words,
for the EVERYONE user, clear the check box next to Manage Rule
Sets.

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

Set up secondary and tertiary 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.

Storing jobs and input files on servers


Prinergy servers can store jobs or input files. Storing some or all jobs on servers
other than the primary server increases the performance of the primary server.
When you share and designate a folder to store jobs, it is called a job volume. The
server then becomes a job home.
When you share and designate a folder to store input files, it is called an input
volume.
The name of a job volume usually uses the following format:
● Windows: The job volume must start with AraxiVolume_, usually Arax
iVolume_<server name>_<drive letter>, such as AraxiVol
ume_SERVER1_G.
● Mac: Jobs on <server name> <drive letter> Drive , such as
Jobs on Server1 G Drive.

Storing JTPs on servers


A secondary server can run some or all JTPs to facilitate distributed processing.
It is possible to have multiple active instances of certain JTPs, depending on your
48 Chapter 6—Servers

Prinergy licensing agreement. For example, a system could have multiple


instances of the Normalizer JTP active on different Prinergy servers in order to
simultaneously process multiple jobs.
CPU-intensive tasks, such as rendering final output, are good candidates for
distribution onto secondary servers. Other typical uses include designating a
secondary server as the InSite software server or the Archiver software server
in your Prinergy system.

How Prinergy accesses servers


The Araxi service—and its user account—enables Prinergy to automatically start
and restart software components on all servers in the system. When the Prinergy
server starts, you must log on to the server and start the Araxi service.
The Araxi service is a Windows operating system service that monitors and
restarts any Prinergy component that terminates unexpectedly. It does this within
the context of groups. For example, if a process with a particular group number
terminates unexpectedly and is going to be restarted, other processes with the
same group number are also stopped and restarted.
Every server in the Prinergy system must have a user account with an identical
user name and password so that the Araxi service—as well as the
AraxiBackupManager service—can access every server.
● The default user name of this account is ARAXI.
● You can change the user name and password, but both the user name and
password must be the same on every server in the system. If you change the
user name or password, make sure you change them on every Prinergy server.
● You can change the password to increase system security---for example, if
an unauthorized user discovers the password.
Important: Limit knowledge of the Araxi service account password to authorized
users only. Users who log on to the system using the Araxi service account have
administrative access to the Prinergy system. For example, they can edit user
accounts and system settings.
Setting up a secondary server 49

Setting up a secondary server


Configure a Windows server as a secondary server in the Prinergy system.

Creating an Araxi service account on a Windows server


Create a user account that the Araxi service uses to access the Windows
server.
If the Araxi service account is set up on the domain controller, skip this
procedure because the domain account applies to all Windows servers
in the domain.

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.

3. Enable the user rights for the Araxi service account:


a. From the Start menu, select Programs > Administrative Tools >
Local Security Policy.
b. On the Tree tab, expand Local Policies, and select User Rights
Assignment.
The right pane displays a list of user rights.
c. In the right pane, right-click Act as part of the operating system
and select Security or Properties.
d. Click Add or Add User or Group, and 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.
e. In the right pane, right-click Log on as a service, and select Security
or Properties.
50 Chapter 6—Servers

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.

Creating a job or input volume on a Windows server


Create a folder on a Windows server that you can use to store jobs or
input files.

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

2. Share the folder that you created:


a. On the desktop, right-click My Computer, and select Manage.
b. In the left pane, expand Shared Folders, and right-click Shares,
and select New File Share.
If you are using Windows Server® 2003, follow the prompts in the
Share a Folder Wizard.
c. Select the Microsoft Windows check box.
d. Click Browse, and select the folder that you want to share.
e. In the Share name box, type a name using the correct format.
For a job volume, use the format AraxiVolume_<server
name>_<drive letter>, such as AraxiVolume_SERV
ER1_G. The share name must start with the prefix AraxiVol
ume_.
For an input volume, you can use any format, such as InputFiles.
f. (Optional) In the Share description box, type a description for the
share, such as Prinergy Jobs Volume or Prinergy Input Volume.
g. If your Prinergy system includes Mac client computers using AFP
file-sharing protocol, select the Apple Macintosh check box, and
Adding a secondary server to the system 51

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.

Adding a secondary server to the system


Identify a Windows server as a secondary server in Prinergy Administrator.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Servers tab.
3. Next to the Secondary Servers box, click Add Server.
4. Where prompted, type the name of the server that you want to add.
5. In the Logon As box, type a user name and password for an account
that has administrative privileges.
6. Click OK.
7. Stop and restart the Prinergy system.
52 Chapter 6—Servers

Adding a server to the HOSTS file of the other servers


Add the IP address and name of a new server to the HOSTS file of the
Prinergy primary server.
If your network has a Domain Name System (DNS) server, do not use
this procedure. Instead, add the IP address and name of the new server
to the DNS server.

1. Locate the following folder:


● Windows 2000: D:\WINNT\system32\drivers\etc
● Windows 2003: C:\Windows\system32\drivers\etc

2. In a text editor, open the HOSTS file.


3. Add a line that identifies the server's IP address and name, in this
format:
<IP address> <host name>
where <IP address> is the IP address of the server
where <host name> is the DNS name of the server
4. Save and close the file.
Do not accidentally add a file name extension, such as .txt.
5. Repeat the procedure on each server in the Prinergy system.
The changes take effect immediately. You do not need to restart Prinergy.

Setting up a tertiary server


Set up tertiary servers to store job folders and/or input files for Prinergy
jobs.

Qualified tertiary servers and Mac client computer file-sharing


protocols
Tertiary servers are qualified for use with Prinergy only using specific
network file-sharing protocols to and from Mac client computers. Each
operating system or platform has a defined service level.
Note: Service levels are described below the table.
Setting up a tertiary server 53

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.

Windows 2003 Server Cluster AFP with ExtremeZ-IP Service level 3


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.

Windows Server 2008 Not currently qualified Not currently qualified


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.

Isilon SMB with AppleDouble Service level 1


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 descriptions


Service level 1 The solution is documented, tested with every major and
minor upgrade, and fully supported, which means problems
are investigated.
Service level 2 The solution is documented and tested with every major
upgrade but not directly supported.
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.

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

Limitations across all solutions


Note: Kodak does not support, and assumes no responsibility for, problems or
performance issues that may occur as a result of using third-party products.
Problems related to third-party products are not covered by Kodak service
contracts.
● All servers in your Prinergy system must use the same Mac client computer
protocol. Otherwise, Mac users may unknowingly mount the a volume using
the wrong protocol, which might cause data loss.
● The Job Replication option cannot be used with any third-party tertiary server.
If you want to replicate jobs, you must buy a server from your Prinergy supplier
or find an alternate solution.
● A storage area network connected to a tertiary server is qualified and
supported, according to the operating system of the tertiary server that it is
connected to.

Solutions that are permitted but not qualified


● UNIX tertiary server supported by running an NFS client, such as SFU, on all
Prinergy primary and secondary servers: This solution is not qualified—it is
not documented, tested, or supported. Use it at your own risk.NFS has many
known problems and many potential problems, because Microsoft does not
test the solution on all variants of UNIX. If you use this solution, use it only
for input volumes, not for job volumes.
● Network-attached storage other than Isilon: This solution is not qualified—it
is not documented, tested, or supported.Use it at your own risk. If you use
this solution, use it only for input volumes, not for job volumes.
● Storage area network directly connected to the Prinergy primary server: This
solution is not qualified—it is not documented, tested, or supported.
● All other configurations not identified above or in the above table.

Setting up a Windows tertiary server


Configure a Windows server as a tertiary server in the Prinergy system.
1. Creating an Araxi service account on a Windows server
2. Creating a job or input volume on a Windows server
3. Adding a server to the HOSTS file of the other servers
4. Adding a tertiary server or input volume to the system
5. Identifying non-SFM servers in the OTHERHOSTS file
6. Testing a tertiary server
56 Chapter 6—Servers

Creating an Araxi service account on a Windows server


Create a user account that the Araxi service uses to access the Windows
server.
If the Araxi service account is set up on the domain controller, skip this
procedure because the domain account applies to all Windows servers
in the domain.

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.

3. Enable the user rights for the Araxi service account:


a. From the Start menu, select Programs > Administrative Tools >
Local Security Policy.
b. On the Tree tab, expand Local Policies, and select User Rights
Assignment.
The right pane displays a list of user rights.
c. In the right pane, right-click Act as part of the operating system
and select Security or Properties.
d. Click Add or Add User or Group, and 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.
e. In the right pane, right-click Log on as a service, and select Security
or Properties.
Creating a job or input volume on a Windows server 57

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.

Creating a job or input volume on a Windows server


Create a folder on a Windows server that you can use to store jobs or
input files.

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

2. Share the folder that you created:


a. On the desktop, right-click My Computer, and select Manage.
b. In the left pane, expand Shared Folders, and right-click Shares,
and select New File Share.
If you are using Windows Server 2003, follow the prompts in the
Share a Folder Wizard.
c. Select the Microsoft Windows check box.
d. Click Browse, and select the folder that you want to share.
e. In the Share name box, type a name using the correct format.
For a job volume, use the format AraxiVolume_<server
name>_<drive letter>, such as AraxiVolume_SERV
ER1_G. The share name must start with the prefix AraxiVol
ume_.
For an input volume, you can use any format, such as InputFiles.
f. (Optional) In the Share description box, type a description for the
share, such as Prinergy Jobs Volume or Prinergy Input Volume.
g. If your Prinergy system includes Mac client computers using AFP
file-sharing protocol, select the Apple Macintosh check box, and
58 Chapter 6—Servers

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.

Adding a server to the HOSTS file of the other servers


Add the IP address and name of a new server to the HOSTS file of the
Prinergy primary server.
If your network has a Domain Name System (DNS) server, do not use
this procedure. Instead, add the IP address and name of the new server
to the DNS server.

1. Locate the following folder:


● Windows 2000: D:\WINNT\system32\drivers\etc
● Windows 2003: C:\Windows\system32\drivers\etc

2. In a text editor, open the HOSTS file.


3. Add a line that identifies the server's IP address and name, in this
format:
<IP address> <host name>
where <IP address> is the IP address of the server
where <host name> is the DNS name of the server
Adding a tertiary server or input volume to the system 59

4. Save and close the file.


Do not accidentally add a file name extension, such as .txt.
5. Repeat the procedure on each server in the Prinergy system.
The changes take effect immediately. You do not need to restart Prinergy.

Adding a tertiary server or input volume to the system


Use the Configuration Options dialog box to add a tertiary server to the
Prinergy system.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Servers tab.
3. Next to the Tertiary Servers list, click Add Server.
4. Type the server name, or type the UNC path (\\server
name\sharename) of the tertiary server that you want to add.
5. Click OK.
If you want to add this server as an input volume, you can add it now:
6. For an input volume, add the folder as an input volume in Prinergy
Administrator:
a. From the Tools menu, select Configure System.
b. In the Configuration Options dialog box, click the Input Volumes
tab.
c. Click Browse, locate the shared folder, select it, and click OK.
Note: You can also type the name of the tertiary server and the
share name, using the format: \\servername\sharename.

d. Click Add Volume.


e. Click OK.

Identifying non-SFM servers in the OTHERHOSTS file


Edit the otherhosts file to prevent Prinergy from making calls to
non-SFM servers.
Requirements:
The OTHERHOSTS file is located in the %Araxi
Home%\CreoAraxi\etc folder.
60 Chapter 6—Servers

● 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"

4. In the "*:MyServerName"="MyServerName" line, you can either replace


the asterisk (*) with the name of your Mac zone, or leave the asterisk
(*) if you don't want to specify any Mac zone. Replace all instances
of MyServerName with the name of your server.
5. Locate the [shares] section, and add NtHost="MyServerName", add
Mac volume share name=Windows share name, for example "Jobs
on MyServerName J"="AraxiVolume_MyServerName_J", and add
"AraxiPreps"="AraxiPreps" as the last lines.
[shares]
NtHost="NTBLATSERVER1"
"MacVolumeA"="NTShareA"
"MacVolumeB"="NTShareB"
NtHost="NTBLATSERVER2"
"MacVolumeX"="NTShareX"
NtHost="MyServerName"
"Jobs on MyServerName J"="AraxiVolume_MyServerName_J"
"AraxiPreps"="AraxiPreps"

6. Replace all instances of MyServerName with the name of your server.


Testing a tertiary server 61

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"

In Finder, click Go > Connect to Server and type


afp://TertiaryServer to connect to your server. Then
select Jobs on TertiaryServer.

See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128

Testing a tertiary server


After you add a tertiary server, test it to ensure that it is set up correctly.

1. Confirm that the newly added share is accessible:


a. Use Windows Explorer to locate the share on the tertiary server.
b. If you are not logged onto the Windows operating system as the
Araxi service user, you will be prompted for a user name and
password. Type the Araxi service user name and password.
c. Make sure that all of the subfolders in the share are visible in
Windows Explorer.
d. Create a folder in the share.
62 Chapter 6—Servers

e. Create a file in the folder that you created.


f. Delete the file that you just created.
g. Delete the folder that you just created.
2. Test the system:
a. Create a job on the tertiary server, add some input files, and refine
the files.
b. Confirm that the resource forks of the files are created properly.
For example, double-click a PDF file to ensure that it opens in the
Adobe Acrobat software.
c. Test as much of the system as possible by refining, outputting
proofs, and plating.
3. If you intend to use the tertiary server for archiving, archive, purge,
and retrieve a job from the tertiary server.

Setting up a Windows Server 2003 cluster tertiary server


Set up a Windows Server 2003 cluster as a tertiary server to provide
redundancy for a front-end server. (When one cluster node fails, other
cluster nodes can take over tasks that the failed node was performing.)
1. Meeting requirements to use a Windows cluster
2. Installing a Windows 2003 cluster
3. Setting up shared disks on a Windows 2003 cluster
4. Configuring a Windows cluster service
5. Configuring clustered storage
6. Adding resources to the cluster
7. Adding a tertiary server or input volume to the system
8. Configuring AFP with ExtremeZ-IP
9. Identifying non-SFM servers in the OTHERHOSTS file
10. Testing a tertiary server

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

Meeting requirements to use a Windows cluster


Make sure you meet the software, hardware, network, and shared disk
requirements.
This documentation assumes the cluster has two nodes.
● The Prinergy system must be configured with the default connection
for Mac OS X clients set to SMB instead of AFP.
Windows Server 2003 clustering does not support File Services for
Macintosh. Mac OS X or Windows Workshop clients are required for
this system.
● Meet the following software requirements:
● Microsoft Windows Server 2003 Enterprise Edition or Windows
2003 Datacenter Edition
● Prinergy 3.1.0.7. or later software for Mac OS X Workshop client
support (SMB connectivity)
● Cluster nodes must be in a domain environment.
● All nodes must be members of the same domain.
● If the tertiary server is to be used with the InSite Prepress Portal
system in a DMZ configuration, all nodes must have the
InSiteService account. Without this account, Prepress Portal cannot
access jobs on the tertiary server.
● A cluster service account, a domain-level account that is a member
of the local administrators group on each node, is required; a
dedicated account is best.

● Meet the following hardware requirements:


● The cluster hardware must be in the cluster service Windows Server
Catalog. (http://www.windowsservercatalog.com/)
● Two mass storage device controllers—a local system disk for the
operating system to be installed on one controller, and a separate
controller for the shared disks
● Two network adapters on each node in the cluster
● A shared storage device, with cables to connect it to the cluster
nodes
64 Chapter 6—Servers

● Meet the following network requirements:


● The cluster must have a unique NetBIOS name.
● The cluster must be in a domain environment and not a workgroup
environment.
● Each node must have static IP addresses for all network interfaces.
● All nodes must have at least two physically independent LANs for
public and private communication.

● Meet the following shared disk requirements:


● All shared disks, including the quorum disk, must be attached to a
shared bus.
● Shared disks must be on a different controller than the one used
by the system drive.
● Use a dedicated disk (50 MB minimum) as the quorum device. Use
a partition of at least 500 MB for optimal NTFS file system
performance.
● All shared disks must be configured as basic disks.
● All shared disks must be configured as master boot record (MBR)
disks on systems running 64-bit versions of Windows Server 2003.
● All partitions on the clustered disks must be formatted as NTFS.
● For best results, use hardware-fault-tolerant RAID configurations
for all disks.
● For best results, use a minimum of two logical shared drives
(quorum drive and data drive).

Installing a Windows 2003 cluster


Set up a two-node cluster on a Windows 2003 server.
Requirements:
● Install the Windows Server 2003 operating system on both nodes.
● Ensure you have two network adapters.

1. Configure the first network adapter to connect to the production


network with a static IP address. In Network Connections, rename
the first Local Area Connection (LAN) to Public for easier identification.
Do this in both nodes.
Setting up shared disks on a Windows 2003 cluster 65

2. Configure the second network adapter on a separate network with


another static IP address on a different subnet for private cluster
communication:
a. Ensure that the IP address is not on the same subnet or network
as any other public network adapter.
b. Do not enter any default gateway or DNS server addresses.
c. On the WINS tab, verify that no values are defined. Select Disable
NetBIOS over TCP/IP.
d. Use a crossover network cable to connect the two nodes via this
network adapter.
e. For easier identification, in Network Connections, rename the
second Local Area Connection to Private. Do this in both nodes.
3. Configure the binding order of networks in both nodes in the following
order:
a. Public
b. Private
4. Configure the network adapters in the Private LAN to have the same
link speed and duplex mode. Do not use an auto-select setting for
speed, because some adapters may drop packets while determining
speed. You can set the link speed and duplex mode to 100Mbps/Half
Duplex for all adapters in the Private LAN.

Setting up shared disks on a Windows 2003 cluster


Configure the quorum disk and other shared disks.
Set up the shared disks with only the first node running; shut down the
second node. Start the second node only after you install the cluster
service on the first node. The shared disks may be corrupted if you start
both nodes before the cluster service is installed on the first node.

1. Configure the quorum disk:


The quorum disk is used to store cluster configuration database
checkpoints and log files that help manage the cluster and maintain
consistency. Microsoft recommends the following quorum disk
procedures:
66 Chapter 6—Servers

● Create a logical drive with a minimum size of 50 MB to be used as


a quorum disk (500 MB is optimal for NTFS).
● Dedicate a separate disk as a quorum resource.
● Use a volume on a hardware RAID array for the quorum disk.
● Do not use the quorum disk for anything other than cluster
management.
● Q is the standard quorum disk drive letter.

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.

3. Configure other shared disks.


Other shared disks are needed to host the production files. To configure
a shared disk, follow the configuring quorum disk procedure, but use
drive letter R, S, and so on.
4. Verify disk access and functionality:
a. Check that the newly created volumes are accessible from the first
node.
b. Verify that files can be created and copied into the new volumes.
Configuring a Windows cluster service 67

c. Verify that the files in the new volumes can be accessed.


d. Turn off the first node.
e. Turn on the second node and verify that the new volumes are
accessible.
f. Verify that files can be created and copied into the new volumes.
g. Verify that the files in the new volumes can be accessed.
h. Turn off the second node.
i. Turn on the first node.

Configuring a Windows cluster service


Use Cluster Administrator to configure the nodes in the cluster.

1. Configure the first node:


a. Turn off the second node when configuring the cluster on node
one.
b. Log on to node one using a domain account with local administrative
privileges.
c. Run the Cluster Administrator (Start > All Programs >
Administrative Tools > Cluster Administrator).
d. In the Open Connection to Cluster dialog box Action list, select
Create new cluster, and click OK.
e. The New Server Cluster Wizard starts. Verify that you have all the
necessary information to configure the cluster, as listed on the
Welcome page. Click Next.
f. If you have more than one domain in your network, in the Domain
list, select the domain in which the cluster will be created. Type a
unique NetBIOS name for the Cluster name. Click Next.
g. In the Computer name box, type the name of the first node server.
The Advanced option is not covered in this document. For
information about this option, see the Windows Server 2003
clustering documentation.
h. Click Next. The setup process checks the configuration for possible
hardware or software problems. Review any warnings or error
messages. If there are no errors, click Next.
68 Chapter 6—Servers

i. Type a unique IP address that will be used for cluster management.


This cluster IP address should be only used for administrative
purposes and not for client connections. Click Next.
j. In the User name and Password boxes, type the user name and
password of the cluster service account that you created for this
cluster. In the Domain list, select the domain name. Click Next.
k. Review the proposed cluster configuration to verify that the
information that will be used to create the cluster is correct. Click
Next.
l. Verify that all the steps in the creation of the cluster are successful.
Check any warning or error by clicking the plus sign beside it. If the
cluster creation failed, correct the problem and retry cluster
creation. If successful, click Next.
m. Click Finish to complete the cluster installation.
n. Verify that all cluster resources appear online successfully.
2. Configure the second node.
a. Leave node one and the shared storage turned on.
b. Turn on the second node.
c. Log on to node one with a domain account that has local
administrative privileges on all nodes.
d. Open Cluster Administrator on node one.
e. Right-click the cluster and select New > Node.
f. The Add Nodes Wizard starts. Click Next.
g. On the Select Computer page, type the Server name of the second
node. Click Add. Click Next.
h. The setup process checks the configuration for possible hardware
or software problems. Review any warnings or error messages. If
there are no errors, click Next.
i. Type the password for the cluster service account. Click Next.
j. Review the proposed cluster configuration to verify that the
information that will be used to create the cluster is correct. Click
Next.
k. Verify that all the steps in the configuration of the cluster are
successful. Check any warning or error by clicking the plus sign
Configuring clustered storage 69

beside it. If the cluster configuration failed, correct the problem


and retry cluster creation. If successful, click Next.
l. Click Finish to complete the installation.

Configuring clustered storage


Remove disks that will not be used as shared storage.

1. Start Cluster Administrator.


2. Check whether any disks are listed that won't be used as shared
storage.
3. Remove these disks by right-clicking them and selecting Delete.

Adding resources to the cluster


Add an IP address, a network name, and a file-share resource.

1. Add an IP address to which clients can connect:


a. Start Cluster Administrator.
b. Right-click the cluster and select New > Resource.
c. Type a name and description for the IP address resource. In the
Resource type list, select IP address. Select the group where this
resource will belong (do not use Cluster Group). The shared storage
that will be used as the job volume should be in the same group.
Click Next.
d. Add both nodes as possible owners of the resource. Click Next.
e. On the Dependencies page, leave Resource dependencies empty.
Click Next.
f. Type the TCP/IP Address and Subnet mask. Click Finish.
A dialog box should appear with the message that the resource
was created successfully.
g. Bring the resource online by right-clicking it, and selecting Bring
online.
70 Chapter 6—Servers

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.

Adding a tertiary server or input volume to the system


Use the Configuration Options dialog box to add a tertiary server to the
Prinergy system.

1. From the Tools menu, select Configure System.


Setting up a tertiary server 71

2. In the Configuration Options dialog box, click the Servers tab.


3. Next to the Tertiary Servers list, click Add Server.
4. Type the server name, or type the UNC path (\\server
name\sharename) of the tertiary server that you want to add.
5. Click OK.
If you want to add this server as an input volume, you can add it now:
6. For an input volume, add the folder as an input volume in Prinergy
Administrator:
a. From the Tools menu, select Configure System.
b. In the Configuration Options dialog box, click the Input Volumes
tab.
c. Click Browse, locate the shared folder, select it, and click OK.
Note: You can also type the name of the tertiary server and the
share name, using the format: \\servername\sharename.

d. Click Add Volume.


e. Click OK.
72 Chapter 6—Servers

Configuring AFP with ExtremeZ-IP


Install and configure ExtremeZ-IP on a Prinergy primary, secondary, or
tertiary server to enable AFP connections from Mac client computers
without Services for Macintosh (SFM).
Requirements:
● This task applies only if you are using ExtremeZ-IP to enable Mac
client computers to connect via AFP to Windows servers.
● If you are using Prinergy 4.0.2.6, 4.1.2.2, or 5.0.2.0, perform this task
on primary, secondary, or tertiary servers.
If you are using earlier versions, perform this task only on tertiary
servers because ExtremeZ-IP is not supported on primary or secondary
servers on earlier versions.
● Ensure that the server uses a version of Windows that is compatible
with the version of ExtremeZ-IP. For example, ExtremeZ-IP 5.0 is
compatible with Windows 2003 R2 SP2 operating systems but not
Windows NT® Workstation platform, which is used by the Renaissance
scanner.
● Ensure that the server is already part of the Prinergy system.
● Ensure that the Prinergy job volume on the server is not at the root of
a volume. ExtremeZ-IP does not allow shares to be created below
another share. If you create a share at the root of the volume, you
cannot create any other shares on that volume.
● Ensure the volume share name does not exceed 27 characters.

1. If you are installing ExtremeZ-IP on a primary or secondary server,


skip this step because you want ExtremeZ-IP to convert all your
existing Mac shares.
Perform this step only under the following conditions:
● you are installing ExtremeZ-IP on a tertiary server
● you are using 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.
Setting up a tertiary server 73

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.

5. If you see the message The server contains Windows (SMB)


shares. Would you like to replicate these shares as
ExtremeZ-IP volumes?, click No.
74 Chapter 6—Servers

6. On the ExtremeZ-IP Administrator Summary screen, click Settings to


configure ExtremeZ-IP settings.
a. Click the File Server Settings tab.
● Confirm that AFP Port is 548
● Confirm that the Enable home Directory Support check box is
cleared

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

If you migrated shares on a primary or If you did not migrate shares on a


secondary server tertiary server

On the ExtremeZ-IP Administrator On the ExtremeZ-IP Administrator


Summary screen, click Volumes. Summary screen, click Volumes.

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.

Note: In the Volumes window, do not click Migrate SFM Shares.


Close ExtremeZ-IP.
8. After you have set up the ExtremeZ-IP share, re-create the share in
Windows using the folder path you created in the previous step.
a. Right-click My Computer and select Manage.
b. In the Computer Management window, navigate to System Tools
> Shared Folders > Shares.
c. Write down the existing Share Name, for example AraxiVol
ume_MyServerName_J.
d. Right-click the existing share, for example AraxiVolume_My
ServerName_J, and select Stop Sharing.
e. Click Action > New Share and click Next.
f. Click Browse and navigate to the AraxiVolume folder you set up
in the previous step. Click OK and click Next.
g. In the Share a Folder Wizard > Name, Description, and Settings
window, type the same Share Name you just deleted, for example
AraxiVolume_MyServerName_J. Click Next.
76 Chapter 6—Servers

h. In the Share a Folder Wizard > Permissions window, select Use


custom share and folder permissions and click Customize.
i. In the Customize Permissions window, select all the check boxes
under the Allow column. Click OK, click Finish, and click Close.

Next: Stop and restart Prinergy for these changes to take effect.

See also:
Converting to AFP on page 128

Identifying non-SFM servers in the OTHERHOSTS file


Edit the otherhosts file to prevent Prinergy from making calls to
non-SFM servers.
Requirements:
The OTHERHOSTS file is located in the %Araxi
Home%\CreoAraxi\etc folder.
● 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"

4. In the "*:MyServerName"="MyServerName" line, you can either replace


the asterisk (*) with the name of your Mac zone, or leave the asterisk
(*) if you don't want to specify any Mac zone. Replace all instances
of MyServerName with the name of your server.
Setting up a tertiary server 77

5. Locate the [shares] section, and add NtHost="MyServerName", add


Mac volume share name=Windows share name, for example "Jobs
on MyServerName J"="AraxiVolume_MyServerName_J", and add
"AraxiPreps"="AraxiPreps" as the last lines.
[shares]
NtHost="NTBLATSERVER1"
"MacVolumeA"="NTShareA"
"MacVolumeB"="NTShareB"
NtHost="NTBLATSERVER2"
"MacVolumeX"="NTShareX"
NtHost="MyServerName"
"Jobs on MyServerName J"="AraxiVolume_MyServerName_J"
"AraxiPreps"="AraxiPreps"

6. Replace all instances of MyServerName with the name of your server.

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"

In Finder, click Go > Connect to Server and type


afp://TertiaryServer to connect to your server. Then
select Jobs on TertiaryServer.

See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128
78 Chapter 6—Servers

Testing a tertiary server


After you add a tertiary server, test it to ensure that it is set up correctly.

1. Confirm that the newly added share is accessible:


a. Use Windows Explorer to locate the share on the tertiary server.
b. If you are not logged onto the Windows operating system as the
Araxi service user, you will be prompted for a user name and
password. Type the Araxi service user name and password.
c. Make sure that all of the subfolders in the share are visible in
Windows Explorer.
d. Create a folder in the share.
e. Create a file in the folder that you created.
f. Delete the file that you just created.
g. Delete the folder that you just created.
2. Test the system:
a. Create a job on the tertiary server, add some input files, and refine
the files.
b. Confirm that the resource forks of the files are created properly.
For example, double-click a PDF file to ensure that it opens in the
Adobe Acrobat software.
c. Test as much of the system as possible by refining, outputting
proofs, and plating.
3. If you intend to use the tertiary server for archiving, archive, purge,
and retrieve a job from the tertiary server.
Setting up a Brisque tertiary server 79

Setting up a Brisque tertiary server


Configure a server that is running Brisque 4, Brisque Serve, or Brisque 5
as a tertiary server in the Prinergy system.

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.

Creating an Araxi service account on a UNIX server


Create a user account that the Araxi service uses to access the UNIX
server.

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.

Setting up Samba on a Brisque 4 or Brisque Serve server


For a Brisque 4 or Brisque Serve server, install Samba to enable it to
connect to the Prinergy system.
Requirements:
● Get the Samba for Brisque 4.1, Brisque 5, and Brisque Serve Installation
and Configuration Guide.
● Get the Kodak SMB Connectivity for Brisque Serve and Brisque
software (015-00654A), which is a special version of SMB for Brisque
that works seamlessly with Prinergy Archiver.
80 Chapter 6—Servers

● Install Samba.
Follow the instructions in the Samba for Brisque 4.1, Brisque 5, and Brisque
Serve Installation and Configuration Guide.

Setting up Samba and setting up volumes on a Brisque 5 server


For a Brisque 5 server, contact your Kodak service representative to
activate the Samba software and enable it to connect to the Prinergy
system.
Samba is already installed and configured with the Brisque 5 software,
but it is not activated.
● Contact your Kodak service representative to activate Samba and
configure the shares on the Brisque 5 server.

Creating an input volume on a Brisque server


Create a folder on a Brisque server to store input files that Prinergy can
access.
Requirements:
If you do not want to store input files on the server, skip this procedure.
Get the Samba for Brisque 4.1, Brisque 5, and Brisque Serve Installation and
Configuration Guide.
● Create an input volume according to the instructions in the Samba for
Brisque 4.1, Brisque 5, and Brisque Serve Installation and Configuration
Guide.

Creating a job volume on a Brisque server


Create a folder on a Brisque server that you can use to store jobs.
● Contact your Kodak service representative to add the volume.
Adding a server to the HOSTS file of the other servers 81

Adding a server to the HOSTS file of the other servers


Add the IP address and name of a new server to the HOSTS file of the
Prinergy primary server.
If your network has a Domain Name System (DNS) server, do not use
this procedure. Instead, add the IP address and name of the new server
to the DNS server.

1. Locate the following folder:


● Windows 2000: D:\WINNT\system32\drivers\etc
● Windows 2003: C:\Windows\system32\drivers\etc

2. In a text editor, open the HOSTS file.


3. Add a line that identifies the server's IP address and name, in this
format:
<IP address> <host name>
where <IP address> is the IP address of the server
where <host name> is the DNS name of the server
4. Save and close the file.
Do not accidentally add a file name extension, such as .txt.
5. Repeat the procedure on each server in the Prinergy system.
The changes take effect immediately. You do not need to restart Prinergy.

Identifying non-SFM servers in the OTHERHOSTS file


Edit the otherhosts file to prevent Prinergy from making calls to
non-SFM servers.
Requirements:
The OTHERHOSTS file is located in the %Araxi
Home%\CreoAraxi\etc folder.
● 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
82 Chapter 6—Servers

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"

4. In the "*:MyServerName"="MyServerName" line, you can either replace


the asterisk (*) with the name of your Mac zone, or leave the asterisk
(*) if you don't want to specify any Mac zone. Replace all instances
of MyServerName with the name of your server.
5. Locate the [shares] section, and add NtHost="MyServerName", add
Mac volume share name=Windows share name, for example "Jobs
on MyServerName J"="AraxiVolume_MyServerName_J", and add
"AraxiPreps"="AraxiPreps" as the last lines.
[shares]
NtHost="NTBLATSERVER1"
"MacVolumeA"="NTShareA"
"MacVolumeB"="NTShareB"
NtHost="NTBLATSERVER2"
"MacVolumeX"="NTShareX"
NtHost="MyServerName"
"Jobs on MyServerName J"="AraxiVolume_MyServerName_J"
"AraxiPreps"="AraxiPreps"

6. Replace all instances of MyServerName with the name of your server.

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

● 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"

In Finder, click Go > Connect to Server and type


afp://TertiaryServer to connect to your server. Then
select Jobs on TertiaryServer.

See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128

Adding a tertiary server or input volume to the system


Use the Configuration Options dialog box to add a tertiary server to the
Prinergy system.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Servers tab.
3. Next to the Tertiary Servers list, click Add Server.
4. Type the server name, or type the UNC path (\\server
name\sharename) of the tertiary server that you want to add.
5. Click OK.
If you want to add this server as an input volume, you can add it now:
6. For an input volume, add the folder as an input volume in Prinergy
Administrator:
a. From the Tools menu, select Configure System.
b. In the Configuration Options dialog box, click the Input Volumes
tab.
c. Click Browse, locate the shared folder, select it, and click OK.
Note: You can also type the name of the tertiary server and the
share name, using the format: \\servername\sharename.
84 Chapter 6—Servers

d. Click Add Volume.


e. Click OK.

Testing a tertiary server


After you add a tertiary server, test it to ensure that it is set up correctly.

1. Confirm that the newly added share is accessible:


a. Use Windows Explorer to locate the share on the tertiary server.
b. If you are not logged onto the Windows operating system as the
Araxi service user, you will be prompted for a user name and
password. Type the Araxi service user name and password.
c. Make sure that all of the subfolders in the share are visible in
Windows Explorer.
d. Create a folder in the share.
e. Create a file in the folder that you created.
f. Delete the file that you just created.
g. Delete the folder that you just created.
2. Test the system:
a. Create a job on the tertiary server, add some input files, and refine
the files.
b. Confirm that the resource forks of the files are created properly.
For example, double-click a PDF file to ensure that it opens in the
Adobe Acrobat software.
c. Test as much of the system as possible by refining, outputting
proofs, and plating.
3. If you intend to use the tertiary server for archiving, archive, purge,
and retrieve a job from the tertiary server.

Setting up an Xserve tertiary server


Configure an Apple Xserve server as a tertiary server in the Prinergy
system.
1. Creating an Araxi service account on an Xserve server
2. Creating a shared volume with an SMB share on an Xserve server
Creating an Araxi service account on an Xserve server 85

3. Configuring an Xserve server with SMB


4. Adding a server to the HOSTS file of the other servers
5. Identifying non-SFM servers in the OTHERHOSTS file
6. Adding a tertiary server or input volume to the system
7. Testing a tertiary server

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. Select Application > Server > Workgroup Manager.


2. In the Workgroup Manager Connect dialog box, in the Address box,
type the server name or the server IP address, and log on as a user
with administrative privileges.
3. Create the user account:
a. Click Accounts, and in the left pane, click the User tab.
b. Click New User, and on the Basic tab, in the Name box, type Araxi
(the same user account name that is used to start the Araxi service).
c. In the Password box, type the password (the same password that
is used to start the Araxi service).
d. Select the User can administer the server check box.
e. In the Define the administrator's privileges dialog box, select the
Edit user preferences and Edit user account check boxes.
f. Select User can log in, and click Save.
86 Chapter 6—Servers

4. Add the user account to a new or existing user group:


a. Click Accounts, and in the left pane, click the Group tab.
b. Click New Group, and in the Name box, type a name for the
group---for example, Prinergy.
Alternatively, select an existing user group that you created for
connecting to the Prinergy system.
c. Beside the Members list, click the + sign to expand the list. In the
list of user accounts on the left side of the groups, double-click
Araxi to add it to the Prinergy group.
d. Click Save.

Creating a shared volume with an SMB share on an Xserve


server
On the Xserve server, create a volume, or select a volume that you want
to share and that is accessible to the Prinergy primary server.
Requirements:
Configure Windows File Sharing for the selected folder. You can use either
SMB or AFP shares. If you have computers running Mac OS 9, you must
create an AFP share name.
Important: If you use both SMB and AFP shares, you must create a share
name for each protocol. Both share names must be created at the same
directory level. Prinergy will create a Jobs folder within the shared
folders—for example, AraxiVolume_MyServerName\Jobs.
On a tertiary server running Windows NT, the AFP share name is created
in the Jobs folder and the SMB share name is created at the root level.

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

7. In the Everyone box, select Read & Write permissions.


8. Click Save.
9. Click the Protocols tab.
10. In the list, select Windows File Settings.
11. Select the Share this item using SMB check box.
12. Select the Allow SMB guest access check box.
13. In the Custom SMB name box, type the share name for SMB---for
example, AraxiVolume_MyServerName_SMB.
Important: The share name must use the prefix AraxiVolume.

14. Set the oplock option:


● Windows 2000: clear the Enable oplock check box
Note: Windows 2000 has a bug that causes I/O errors. You need
to disable oplock to eliminate these I/O errors even though this
will slow performance.

● Windows 2003: select the Enable oplock check box

15. Select the Enable strict locking check box.


16. In the Assign as follows area, in the Owner, Group, and Everyone
lists, select Read & Write.
17. Click Save.

Configuring an Xserve server with SMB


If you are using the SMB file-sharing protocol, configure the smb.conf
file on the Xserve server.
On the Xserve server, locate the /private/etc/smb.conf file and add the
following line to the [global] section.
[global]
mangled names = no

Then in the Xserve server's Server Manager, restart the Windows service.
88 Chapter 6—Servers

Adding a server to the HOSTS file of the other servers


Add the IP address and name of a new server to the HOSTS file of the
Prinergy primary server.
If your network has a Domain Name System (DNS) server, do not use
this procedure. Instead, add the IP address and name of the new server
to the DNS server.

1. Locate the following folder:


● Windows 2000: D:\WINNT\system32\drivers\etc
● Windows 2003: C:\Windows\system32\drivers\etc

2. In a text editor, open the HOSTS file.


3. Add a line that identifies the server's IP address and name, in this
format:
<IP address> <host name>
where <IP address> is the IP address of the server
where <host name> is the DNS name of the server
4. Save and close the file.
Do not accidentally add a file name extension, such as .txt.
5. Repeat the procedure on each server in the Prinergy system.
The changes take effect immediately. You do not need to restart Prinergy.

Identifying non-SFM servers in the OTHERHOSTS file


Edit the otherhosts file to prevent Prinergy from making calls to
non-SFM servers.
Requirements:
The OTHERHOSTS file is located in the %Araxi
Home%\CreoAraxi\etc folder.
● 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
Setting up a tertiary server 89

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"

4. In the "*:MyServerName"="MyServerName" line, you can either replace


the asterisk (*) with the name of your Mac zone, or leave the asterisk
(*) if you don't want to specify any Mac zone. Replace all instances
of MyServerName with the name of your server.
5. Locate the [shares] section, and add NtHost="MyServerName", add
Mac volume share name=Windows share name, for example "Jobs
on MyServerName J"="AraxiVolume_MyServerName_J", and add
"AraxiPreps"="AraxiPreps" as the last lines.
[shares]
NtHost="NTBLATSERVER1"
"MacVolumeA"="NTShareA"
"MacVolumeB"="NTShareB"
NtHost="NTBLATSERVER2"
"MacVolumeX"="NTShareX"
NtHost="MyServerName"
"Jobs on MyServerName J"="AraxiVolume_MyServerName_J"
"AraxiPreps"="AraxiPreps"

6. Replace all instances of MyServerName with the name of your server.

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

● 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"

In Finder, click Go > Connect to Server and type


afp://TertiaryServer to connect to your server. Then
select Jobs on TertiaryServer.

See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128

Adding a tertiary server or input volume to the system


Use the Configuration Options dialog box to add a tertiary server to the
Prinergy system.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Servers tab.
3. Next to the Tertiary Servers list, click Add Server.
4. Type the server name, or type the UNC path (\\server
name\sharename) of the tertiary server that you want to add.
5. Click OK.
If you want to add this server as an input volume, you can add it now:
6. For an input volume, add the folder as an input volume in Prinergy
Administrator:
a. From the Tools menu, select Configure System.
b. In the Configuration Options dialog box, click the Input Volumes
tab.
c. Click Browse, locate the shared folder, select it, and click OK.
Note: You can also type the name of the tertiary server and the
share name, using the format: \\servername\sharename.
Testing a tertiary server 91

d. Click Add Volume.


e. Click OK.

Testing a tertiary server


After you add a tertiary server, test it to ensure that it is set up correctly.

1. Confirm that the newly added share is accessible:


a. Use Windows Explorer to locate the share on the tertiary server.
b. If you are not logged onto the Windows operating system as the
Araxi service user, you will be prompted for a user name and
password. Type the Araxi service user name and password.
c. Make sure that all of the subfolders in the share are visible in
Windows Explorer.
d. Create a folder in the share.
e. Create a file in the folder that you created.
f. Delete the file that you just created.
g. Delete the folder that you just created.
2. Test the system:
a. Create a job on the tertiary server, add some input files, and refine
the files.
b. Confirm that the resource forks of the files are created properly.
For example, double-click a PDF file to ensure that it opens in the
Adobe Acrobat software.
c. Test as much of the system as possible by refining, outputting
proofs, and plating.
3. If you intend to use the tertiary server for archiving, archive, purge,
and retrieve a job from the tertiary server.
92 Chapter 6—Servers

Setting up a generic UNIX tertiary server


Configure a computer that uses a type of UNIX operating system software
other than Brisque or Xserve as a tertiary server in the Prinergy system.

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.

Creating an Araxi service account on a UNIX server


Create a user account that the Araxi service uses to access the UNIX
server.

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

Installing connectivity software on a generic UNIX server


Install Samba or Microsoft Services for UNIX (SFU) NFS client software
to enable a UNIX server to share files with the Prinergy system.

Set up the connectivity software so that JTPs on other Prinergy servers


can access files on the UNIX server:
● If your Prinergy system uses SMB, obtain and install a version of
Samba that is compatible with your type of UNIX software.
See your UNIX documentation or the installation guides at
http://www.samba.org/.
If the Prinergy primary server uses Windows Server 2003, you
must use Samba 3 or later. Otherwise, Windows 2003 cannot
access a Samba share. This is due to several security requirements
of Windows 2003, including SMB signing and other encryption
differences.
Otherwise, since Samba constantly evolves, there is no single "best"
version to use. Kodak does not test Prinergy with specific versions
of Samba on systems other than what is included in the Brisque
and Brisque Serve software. In general, more recent versions are
better. Start with the most recent version of Samba that is
compatible with your type of UNIX software. If you test it and it
does not perform well, try an older version.
● If your Prinergy system uses AFP, install the Microsoft Services for
UNIX (SFU) NFS client software. See Microsoft Services for UNIX
3.5 Server and Client Installation and Configuration.

Configuring a UNIX share with SMB


If you are using the SMB file-sharing protocol, use this example to
configure a share on a UNIX server.
You can set up one or more shares on a single physical volume, unlike the folder
structure on a Prinergy server that uses the Windows operating system.
This example is the smb.conf file from Samba 3. For full details about each
configuration parameter, see the Samba documentation at http://www.samba.org.
Note: Do not modify the parameters that are in bold type. These must be set
correctly for Prinergy to function. It is possible to modify other settings or add
other settings, but do so at your own risk.
94 Chapter 6—Servers

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

Creating a job or input volume on a UNIX server


Create a folder on a UNIX server to store input files that Prinergy can
access.
If you do not want to store input files on the server, skip this procedure.

1. On the tertiary server, create the folder that you will share.
Adding a server to the HOSTS file of the other servers 95

2. On the tertiary server, share the folder.


Generally, you set the permission to Everyone - full control; however,
if you want to restrict access, ensure that the Araxi service account
has full access. For information about using the operating system to
set folder permissions, see the operating system documentation.

Adding a server to the HOSTS file of the other servers


Add the IP address and name of a new server to the HOSTS file of the
Prinergy primary server.
If your network has a Domain Name System (DNS) server, do not use
this procedure. Instead, add the IP address and name of the new server
to the DNS server.

1. Locate the following folder:


● Windows 2000: D:\WINNT\system32\drivers\etc
● Windows 2003: C:\Windows\system32\drivers\etc

2. In a text editor, open the HOSTS file.


3. Add a line that identifies the server's IP address and name, in this
format:
<IP address> <host name>
where <IP address> is the IP address of the server
where <host name> is the DNS name of the server
4. Save and close the file.
Do not accidentally add a file name extension, such as .txt.
5. Repeat the procedure on each server in the Prinergy system.
The changes take effect immediately. You do not need to restart Prinergy.

Identifying non-SFM servers in the OTHERHOSTS file


Edit the otherhosts file to prevent Prinergy from making calls to
non-SFM servers.
Requirements:
The OTHERHOSTS file is located in the %Araxi
Home%\CreoAraxi\etc folder.
96 Chapter 6—Servers

● 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"

4. In the "*:MyServerName"="MyServerName" line, you can either replace


the asterisk (*) with the name of your Mac zone, or leave the asterisk
(*) if you don't want to specify any Mac zone. Replace all instances
of MyServerName with the name of your server.
5. Locate the [shares] section, and add NtHost="MyServerName", add
Mac volume share name=Windows share name, for example "Jobs
on MyServerName J"="AraxiVolume_MyServerName_J", and add
"AraxiPreps"="AraxiPreps" as the last lines.
[shares]
NtHost="NTBLATSERVER1"
"MacVolumeA"="NTShareA"
"MacVolumeB"="NTShareB"
NtHost="NTBLATSERVER2"
"MacVolumeX"="NTShareX"
NtHost="MyServerName"
"Jobs on MyServerName J"="AraxiVolume_MyServerName_J"
"AraxiPreps"="AraxiPreps"

6. Replace all instances of MyServerName with the name of your server.


Adding a tertiary server or input volume to the system 97

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"

In Finder, click Go > Connect to Server and type


afp://TertiaryServer to connect to your server. Then
select Jobs on TertiaryServer.

See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128

Adding a tertiary server or input volume to the system


Use the Configuration Options dialog box to add a tertiary server to the
Prinergy system.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Servers tab.
3. Next to the Tertiary Servers list, click Add Server.
4. Type the server name, or type the UNC path (\\server
name\sharename) of the tertiary server that you want to add.
5. Click OK.
If you want to add this server as an input volume, you can add it now:
98 Chapter 6—Servers

6. For an input volume, add the folder as an input volume in Prinergy


Administrator:
a. From the Tools menu, select Configure System.
b. In the Configuration Options dialog box, click the Input Volumes
tab.
c. Click Browse, locate the shared folder, select it, and click OK.
Note: You can also type the name of the tertiary server and the
share name, using the format: \\servername\sharename.

d. Click Add Volume.


e. Click OK.

Testing a tertiary server


After you add a tertiary server, test it to ensure that it is set up correctly.

1. Confirm that the newly added share is accessible:


a. Use Windows Explorer to locate the share on the tertiary server.
b. If you are not logged onto the Windows operating system as the
Araxi service user, you will be prompted for a user name and
password. Type the Araxi service user name and password.
c. Make sure that all of the subfolders in the share are visible in
Windows Explorer.
d. Create a folder in the share.
e. Create a file in the folder that you created.
f. Delete the file that you just created.
g. Delete the folder that you just created.
2. Test the system:
a. Create a job on the tertiary server, add some input files, and refine
the files.
b. Confirm that the resource forks of the files are created properly.
For example, double-click a PDF file to ensure that it opens in the
Adobe Acrobat software.
c. Test as much of the system as possible by refining, outputting
proofs, and plating.
Monitoring servers 99

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

indicates primary server (running)

indicates secondary server (running)


Server Type (by icon)
indicates primary server (stopped)

indicates secondary server (stopped or unable to log on to the primary server)

Server Name User-defined

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.

Starting: Prinergy Server is in the process of starting up.


Running: Prinergy Server is running and operational.
Server Status Stopping: Prinergy Server is in the process of stopping.
Stopped: Prinergy Server has stopped.
Unable to log onto server: Prinergy Administrator cannot log onto the primary server.
100 Chapter 6—Servers

Changing server configurations


When you add or remove servers from the system, update Prinergy
configurations.

Selecting a network card on the primary server


If the Prinergy primary server has more than one network card, select the
network card that you want Prinergy to use to access the LAN.
Requirements:
You must log on with an account that has administrator privileges.
An example scenario: If you install a new Prinergy primary server which
you connect to an output device (for example, a Magnus™ platesetter)
using a GMCE connection, often the IP address of the output device NIC
(Network Interface Card) is loaded onto the registry instead of the IP
address of the NIC that Prinergy uses for network access. Use this
procedure to correct the registry.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, select the Network Cards
tab.
3. In the Select IP address to use list, select the network card that you
want to use, and click OK.
The registry is updated to use the selected NIC for Prinergy network data
transmission.

Removing an input volume


Remove an input volume from a server.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Input Volumes tab.
3. In the Input Volumes list, select the volume that you want to remove.
4. Click Remove Volume.
Removing a server 101

Removing a server
Remove a server from the Prinergy system when you no longer need the
server.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, select the server that you
want to remove:
To Remove Description

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.

3. Click Remove Server next to the selected server.


Important: Before clicking Remove Server, make sure that you want
to remove the server. Prinergy automatically removes the server from
the system; you are not prompted before the server is removed.

Next:
Update the HOSTS file.

Updating the OTHERHOSTS file to change a non-Windows server


When you change or delete a non-Windows server in the Prinergy system,
update the OTHERHOSTS file using the AFP Mapping dialog box.
Update the OTHERHOSTS file:
● On the primary server and on every secondary server in the Prinergy
system
● No matter what file-sharing protocol you use. This procedure is
required whether you are using AFP (Apple File Protocol) or SMB
(Server Message Block) file-sharing protocol.
● Using the AFP Mapping dialog box—not by editing the OTHERHOSTS
file directly
102 Chapter 6—Servers

If the OTHERHOSTS file does not contain accurate information about a


non-Windows server, users at Mac client computers do not have full
access to files on the server. For example, they cannot double-click a PDF
file to open it in the Acrobat software, and they cannot open the job folder
from within Workshop. They must manually mount the volume.

1. From the Tools menu, select AFP Mapping.


The AFP Mapping dialog box displays a list of every non-Windows
volume that has been added to the Prinergy system. You can work
with each row, but you cannot add or remove rows.
2. Highlight the server and volume.
3. Perform either of the following actions:
● Click Modify AFP Mapping, and click Yes to confirm that you want
to modify the mapping information. In the AFP Mapping dialog box,
enter your changes, and click Modify.
● Click Remove AFP Mapping, and click Yes to confirm that you
want to remove the mapping.
Refer to the following table:
In This Box Type This

AFP Zone Mac zone name—for example, TestLab

AFP Server Mac volume server name—for example, MacServer

AFP Volume Mac volume name—for example, TestVolume.1.0

4. Repeat the previous steps on each primary and secondary server in


the Prinergy system.
5. Stop and restart the Prinergy system. (The new AFP mappings will
not take effect until you restart Prinergy.)

Changing the password of the Araxi service in a domain


If you are in a Windows domain and you want to change the password
of the Araxi service account, make the change on the domain controller.

1. On a domain controller, log on as a domain administrator.


Changing the name of the Araxi service account 103

2. Change the password:


a. From the Start menu, select Programs > Administrative Tools >
Active Directory Users and Computers.
b. On the Tree tab, click the domain node to expand the tree.
c. Select the folder that contains the Araxi service account.
The default account is called Araxi.
If you are not using folders to organize your accounts, the Araxi
service account is typically under Users.
d. Right-click the Araxi service account, and select Reset Password.
e. In the Password and Confirm Password boxes, type a password.
f. Clear the User must change password at next logon check box,
and click OK.

Changing the name of the Araxi service account


Change the name of the user account that the Araxi service uses to access
Prinergy servers.
Next: If the Prinergy system includes any non-Windows servers, delete
the Araxi service user account on each server and create the user account
with the new name.
Creating the Araxi service account in a Windows domain
If you are in a Windows domain, use the domain controller to create the
user account that the Araxi service uses to access Windows servers in
the Prinergy system.
Requirements: If you are re-creating the Araxi service user account in
the entire Prinergy system, shut down all servers in the system before
you log on to the domain controller.

1. On a domain controller, log on as a domain administrator.


2. Create the user account:
a. From the Start menu, select Programs > Administrative Tools >
Active Directory Users and Computers.
b. On the Tree tab, click the domain node to expand the tree.
c. Select the folder that contains the Araxi service account.
The default account is called Araxi.
104 Chapter 6—Servers

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.

3. Enable the user rights for the Araxi service account:


a. From the Start menu, select Programs > Administrative Tools >
Local Security Policy.
b. On the Tree tab, expand Local Policies, and select User Rights
Assignment.
The right pane displays a list of user rights.
c. In the right pane, right-click Act as part of the operating system
and select Security or Properties.
d. Click Add or Add User or Group, and 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.
e. In the right pane, right-click Log on as a service, and select Security
or Properties.
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.

Creating an Araxi service account on a Windows server


Create a user account that the Araxi service uses to access the Windows
server.
If the Araxi service account is set up on the domain controller, skip this
procedure because the domain account applies to all Windows servers
in the domain.

1. Log on as an administrator.
Changing server configurations 105

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.

3. Enable the user rights for the Araxi service account:


a. From the Start menu, select Programs > Administrative Tools >
Local Security Policy.
b. On the Tree tab, expand Local Policies, and select User Rights
Assignment.
The right pane displays a list of user rights.
c. In the right pane, right-click Act as part of the operating system
and select Security or Properties.
d. Click Add or Add User or Group, and 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.
e. In the right pane, right-click Log on as a service, and select Security
or Properties.
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.
106 Chapter 6—Servers

Setting logon rights for the Araxi service account


If you re-create the user account for the Araxi service so that it has a user
name other than "Araxi," change the Araxi service and the
AraxiBackupManager service so that they log on to Prinergy servers using
the new user account. Do this on every Windows operating system server
in the Prinergy system.
Requirements: You must be logged on to the Prinergy system as an
administrator.

1. On the Prinergy primary server, open the Services window:


a. From the Start menu, select Settings > Control Panel.
b. Double-click Administrative Tools.
c. Double-click Services.
2. In the Services window, set the account that the Araxi service uses:
a. in the right pane, right-click Araxi and select Properties.
b. Click the Log On tab.
c. Select This account, and type the name of the account that you
want to use as the service account.
If you are using a domain account, type the full account name,
including the domain prefix—for example, Prinergy\Araxi, where
Prinergy is the domain and Araxi is the account name.
d. In the Password and Confirm Password boxes, type the password
of the Araxi service user account, and click OK.
3. In the Services window, set the account that the Araxi service uses:
a. in the right pane, right-click AraxiBackupManager and select
Properties.
b. Click the Log On tab.
c. Select This account, and type the name of the account that you
want to use as the Araxi service account.
If you are using a domain account, type the full account name,
including the domain prefix—for example, Prinergy\Araxi, where
Prinergy is the domain and Araxi is the account name.
d. In the Password and Confirm Password boxes, type the password
of the Araxi service user account, and click OK.
7 Mac client computer
protocols

Qualified tertiary servers and Mac client computer


file-sharing protocols
Tertiary servers are qualified for use with Prinergy only using specific
network file-sharing protocols to and from Mac client computers. Each
operating system or platform has a defined service level.
Note: Service levels are described below the table.

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.

Windows 2003 Server Cluster AFP with ExtremeZ-IP Service level 3


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.

Windows Server 2008 Not currently qualified Not currently qualified


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.
108 Chapter 7—Mac client computer protocols

Tertiary server Mac client computer protocol Service level and comments

Isilon SMB with AppleDouble Service level 1


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

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 descriptions


Service level 1 The solution is documented, tested with every major and
minor upgrade, and fully supported, which means problems
are investigated.
Service level 2 The solution is documented and tested with every major
upgrade but not directly supported.
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.
Qualified tertiary servers and Mac client computer file-sharing protocols 109

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.

Limitations across all solutions


Note: Kodak does not support, and assumes no responsibility for, problems or
performance issues that may occur as a result of using third-party products.
Problems related to third-party products are not covered by Kodak service
contracts.
● All servers in your Prinergy system must use the same Mac client computer
protocol. Otherwise, Mac users may unknowingly mount the a volume using
the wrong protocol, which might cause data loss.
● The Job Replication option cannot be used with any third-party tertiary server.
If you want to replicate jobs, you must buy a server from your Prinergy supplier
or find an alternate solution.
● A storage area network connected to a tertiary server is qualified and
supported, according to the operating system of the tertiary server that it is
connected to.

Solutions that are permitted but not qualified


● UNIX tertiary server supported by running an NFS client, such as SFU, on all
Prinergy primary and secondary servers: This solution is not qualified—it is
not documented, tested, or supported. Use it at your own risk.NFS has many
known problems and many potential problems, because Microsoft does not
test the solution on all variants of UNIX. If you use this solution, use it only
for input volumes, not for job volumes.
● Network-attached storage other than Isilon: This solution is not qualified—it
is not documented, tested, or supported.Use it at your own risk. If you use
this solution, use it only for input volumes, not for job volumes.
● Storage area network directly connected to the Prinergy primary server: This
solution is not qualified—it is not documented, tested, or supported.
● All other configurations not identified above or in the above table.
110 Chapter 7—Mac client computer protocols

List of Mac client computer file-sharing protocols and


related software
Mac client computers can connect to a Prinergy primary server using
several protocols over several types of software.

Protocols for connecting Mac client computers in Prinergy


SMB
Server Message Block protocol, which is built into the
Windows operating system
SMB is also known as CIFS and Microsoft Windows network.
On UNIX servers, SMB can be implemented with the Samba
software.
SMB handles file resources in the following ways:
● With AppleDouble, using the AppleDouble file format for
foreign files
AppleDouble stores file resources in separate files with a
._ prefix. For example, a file named input.pdf has a
corresponding AppleDouble file that is named ._in
put.pdf.
● With ADS, storing file resources in alternate data streams
(ADS)

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.

Software to assist Mac client computer connections


SFM Microsoft Services for Macintosh, which is built into the
Windows Server 2000 and Windows Server 2003 operating
systems to provide AFP connections for Mac client computers
ExtremeZ-IP File server software that you can install on a Windows server
to provide AFP connections for Mac client computers.
Limitations of Mac client computer file-sharing protocols 111

Samba Open-source file server software that you can install on a


UNIX tertiary server to provide SMB connections for the
Windows Prinergy primary and secondary servers
Helios Software that provides AFP connections on a UNIX server
Xinet Software that provides AFP connections on a UNIX server
SFU Services for UNIX, which you can install on a Windows server
to provide NFS connections

Limitations of Mac client computer file-sharing protocols


Many Mac client computer protocols have significant limitations in a
Prinergy system.

SMB with ADS


SMB with alternate data streams is available when all Mac client computers run
Mac OS X 10.5.

SMB with AppleDouble format


SMB with AppleDouble format has the following limitations:
● Files copy more slowly when you copy a large number of small files. The
per-file overhead is doubled because there are two files.
● When InSite users upload or download files, resources are lost because InSite
is not AppleDouble enabled. This issue applies to both Windows and Mac
client computers. This issue is not significant because InSite primarily uses
PDF files.
● If some Mac client computers use Mac OS X 10.4.7 or earlier, the operating
system may leave files open, locking them from other users. To avoid this
issue, upgrade all Mac client computers to Mac OS X 10.4.8 or later.
● Fonts used in Font Converter do not have file resources, because Font
Converter works only with font files that have resource forks stored in
alternate data streams. You must use the Fork Translator software to manually
convert the font files' resources from AppleDouble to ADS.
● Files restored by Microsoft Backup from Prinergy archiver tapes do not have
file resources, because Microsoft Backup does not create the AppleDouble
files required by SMB. If you want resources for files restored by Microsoft
Backup, you must use the Fork Translator software to manually convert the
files' resources from ADS to AppleDouble.

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

AFP with ExtremeZ-IP does not have any significant limitations.


AFP with SFM has the following limitations:
● Does not support long file names (31 characters or longer)
● Is associated with problems on Mac client computers, such as corrupted
desktops
● Has a limited life span. In the Windows 2003 operating system, Microsoft
does not support SFM. As of Windows 2008, SFM will not exist.
● Is not scalable
● Results in slower Prinergy performance under heavy loads
● Has indexing problems
● Limits the volume size to a maximum of 2 GB

NFS
NFS is not qualified for use with Prinergy, so its limitations are not relevant.

See also:
File resources on page 112

Understanding file resources


Files have resources, such as icons that appears next to the file name in
a file browser.

File resources
The Mac OS and the Windows operating system store file resources in
different ways.

What file resources are


File resources are descriptive information about files, such as:
● File type
● Icons that appear in a file browser
● Preview images
● Originating software

What happens when you don't have file resources


The Mac OS and the Windows operating system store file resource information
in different ways, so files stored in one operating system lack resources when
opened in the other operating system.
Storing file resources 113

If a file lacks resources:


● If you double-click the file in the Prinergy Workshop software or in a file
browser, the file does not open in its originating software.
● The file name extension is missing in the Workshop software and in a file
browser.
● The Kind column is blank in the Workshop software and in a file browser.
● The file icon is missing in a file browser.
● The Get Info dialog box in the Workshop software does not display a preview
image, and the Open With and Kind fields are blank.
Resources do not affect how Prinergy processes files. Prinergy processes files
the same way, regardless of whether they have resources. The exception is Font
Converter as mentioned in Limitations of Mac client computer file-sharing
protocols.

See also:
Limitations of Mac client computer file-sharing protocols on page 111

Storing file resources


File resources can be stored in forks, AppleDouble files, or alternate data
streams.

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.

Alternate data streams (ADS)


Alternate data streams allow files to be associated with more than one data
stream. One use of ADS is to store resources.
The New Technology File System (NTFS) of the Windows operating system and
Isilon support alternate data streams.
SFM and ExtremeZ-IP store resources in an alternate data stream named
AFP_Resource.
114 Chapter 7—Mac client computer protocols

Other
Other platforms, such as EtherShare and Xinet, store resources in separate files
with special file name extensions.

Archiving and Mac client computer file-sharing protocols


Prinergy archives, retrieves, and restores appropriately when you change
protocols.
When you retrieve files that were archived under a different protocol,
Prinergy converts the resource information to the appropriate format.
For example, if you archive jobs under AFP and then convert to SMB with
AppleDouble, when Prinergy retrieves the files, it converts the resource
information from resource forks into AppleDouble files. If files contain
resource information in both AppleDouble files and resource forks, the
Prinergy system uses the resource information required by the current
protocol and ignores the other resource information.

Setting up Mac client computer file-sharing protocols


Starting SFM to support AFP
Start Microsoft Services For Macintosh (SFM), if necessary.
● This task applies only if you are using using SFM to enable Mac client
computers to connect via AFP to Windows servers.
● Perform this task on each Windows server in the Prinergy system.

1. Right-click My Computer and select Manage.


2. In the Computer Management window, expand Services and
Applications and click Services.
3. In the right pane, right-click File Server for Macintosh and select
Properties.
4. In the Startup type list, select Automatic and click Apply.
5. Click Start and then click OK.
6. In the right pane, right-click Print Server for Macintosh and select
Properties.
7. In the Startup type list, select Automatic and click Apply.
Configuring AFP with ExtremeZ-IP 115

8. Click Start and click OK.

See also:
Converting to AFP on page 128

Configuring AFP with ExtremeZ-IP


Install and configure ExtremeZ-IP on a Prinergy primary, secondary, or
tertiary server to enable AFP connections from Mac client computers
without Services for Macintosh (SFM).
Requirements:
● This task applies only if you are using ExtremeZ-IP to enable Mac
client computers to connect via AFP to Windows servers.
● If you are using Prinergy 4.0.2.6, 4.1.2.2, or 5.0.2.0, perform this task
on primary, secondary, or tertiary servers.
If you are using earlier versions, perform this task only on tertiary
servers because ExtremeZ-IP is not supported on primary or secondary
servers on earlier versions.
● Ensure that the server uses a version of Windows that is compatible
with the version of ExtremeZ-IP. For example, ExtremeZ-IP 5.0 is
compatible with Windows 2003 R2 SP2 operating systems but not
Windows NT Workstation platform, which is used by the Renaissance
scanner.
● Ensure that the server is already part of the Prinergy system.
● Ensure that the Prinergy job volume on the server is not at the root of
a volume. ExtremeZ-IP does not allow shares to be created below
another share. If you create a share at the root of the volume, you
cannot create any other shares on that volume.
● Ensure the volume share name does not exceed 27 characters.

1. If you are installing ExtremeZ-IP on a primary or secondary server,


skip this step because you want ExtremeZ-IP to convert all your
existing Mac shares.
Perform this step only under the following conditions:
● you are installing ExtremeZ-IP on a tertiary server
● you are using SFM to support AFP
Stop and disable the SFM services on all Windows operating system
servers in the Prinergy system:
116 Chapter 7—Mac client computer protocols

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.
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.

5. If you see the message The server contains Windows (SMB)


shares. Would you like to replicate these shares as
ExtremeZ-IP volumes?, click No.
Setting up Mac client computer file-sharing protocols 117

6. On the ExtremeZ-IP Administrator Summary screen, click Settings to


configure ExtremeZ-IP settings.
a. Click the File Server Settings tab.
● Confirm that AFP Port is 548
● Confirm that the Enable home Directory Support check box is
cleared

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

If you migrated shares on a primary or If you did not migrate shares on a


secondary server tertiary server

On the ExtremeZ-IP Administrator On the ExtremeZ-IP Administrator


Summary screen, click Volumes. Summary screen, click Volumes.

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.

Note: In the Volumes window, do not click Migrate SFM Shares.


Close ExtremeZ-IP.
8. After you have set up the ExtremeZ-IP share, re-create the share in
Windows using the folder path you created in the previous step.
a. Right-click My Computer and select Manage.
b. In the Computer Management window, navigate to System Tools
> Shared Folders > Shares.
c. Write down the existing Share Name, for example AraxiVol
ume_MyServerName_J.
d. Right-click the existing share, for example AraxiVolume_My
ServerName_J, and select Stop Sharing.
e. Click Action > New Share and click Next.
f. Click Browse and navigate to the AraxiVolume folder you set up
in the previous step. Click OK and click Next.
g. In the Share a Folder Wizard > Name, Description, and Settings
window, type the same Share Name you just deleted, for example
AraxiVolume_MyServerName_J. Click Next.
Identifying non-SFM servers in the OTHERHOSTS file 119

h. In the Share a Folder Wizard > Permissions window, select Use


custom share and folder permissions and click Customize.
i. In the Customize Permissions window, select all the check boxes
under the Allow column. Click OK, click Finish, and click Close.

Next: Stop and restart Prinergy for these changes to take effect.

See also:
Converting to AFP on page 128

Identifying non-SFM servers in the OTHERHOSTS file


Edit the otherhosts file to prevent Prinergy from making calls to
non-SFM servers.
Requirements:
The OTHERHOSTS file is located in the %Araxi
Home%\CreoAraxi\etc folder.
● 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"

4. In the "*:MyServerName"="MyServerName" line, you can either replace


the asterisk (*) with the name of your Mac zone, or leave the asterisk
(*) if you don't want to specify any Mac zone. Replace all instances
of MyServerName with the name of your server.
120 Chapter 7—Mac client computer protocols

5. Locate the [shares] section, and add NtHost="MyServerName", add


Mac volume share name=Windows share name, for example "Jobs
on MyServerName J"="AraxiVolume_MyServerName_J", and add
"AraxiPreps"="AraxiPreps" as the last lines.
[shares]
NtHost="NTBLATSERVER1"
"MacVolumeA"="NTShareA"
"MacVolumeB"="NTShareB"
NtHost="NTBLATSERVER2"
"MacVolumeX"="NTShareX"
NtHost="MyServerName"
"Jobs on MyServerName J"="AraxiVolume_MyServerName_J"
"AraxiPreps"="AraxiPreps"

6. Replace all instances of MyServerName with the name of your server.

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"

In Finder, click Go > Connect to Server and type


afp://TertiaryServer to connect to your server. Then
select Jobs on TertiaryServer.

See also:
Converting to SMB with AppleDouble on page 124
Converting to AFP on page 128
Updating the SFMHOSTS file 121

Updating the SFMHOSTS file


Update the SFMHOSTS file if you use SFM (Services for MacIntosh).
● Perform this task only on tertiary servers.
● This task applies only if you are using using SFM to enable Mac client
computers to connect via AFP to Windows servers.
● Perform this task when you add a server, remove a server, or change
the name or IP address of a server.

1. Open the %AraxiHome%\CreoAraxi\etc\SFMHOSTS file in a


text editor.
2. In the [/etc/sfmhosts] section of the file, add an entry in the following
format: "zone:sfmservername"="ntservername"
If there are no zones on your system, type "*" for the zone.
3. Save and close the file.
Do not accidentally add a file name extension, such as .txt.

Next: Stop and restart Prinergy for these changes to take effect.

Enabling Preps under SMB


In some network configurations, you must enable integrated Preps on
Mac client computers when you use SMB with AppleDouble.
Use this procedure only if you use SMB with AppleDouble as your Mac
client computer protocol and if you use integrated Preps on Mac client
computers that are not in the same domain as the primary server. This
122 Chapter 7—Mac client computer protocols

prevents the error message Could not locate the PrepsPrinergy.cfg


template file.

Perform one of the following tasks on each client computer:


With this Do this
version

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

Changing Mac client computer file-sharing protocols


You can change your Mac client computer protocol to AFP or to SMB
with AppleDouble, and you can convert resources in existing files on job
shares.

Limitations of protocol conversions using Prinergy Administrator


Prinergy Administrator's ability to convert from AFP to SMB or to AFP
from SMB with AppleDouble has several limitations.

Files on non-Windows servers require manual conversion


Prinergy Administrator can convert only volumes that run on the Windows
operating system. Prinergy Administrator cannot convert UNIX volumes, Xserve
volumes, or volumes with any operating system other than Windows. If you have
UNIX and Xserve volumes, you must manually convert them.

Some files are not converted on Windows volumes


Prinergy Administrator does not convert the following files on Windows volumes:
● Files that are open during the conversion
● Files with names that contain certain special characters, such as * | \ / ? < >
● Files that are located on system volumes, in the Recycle Bin, or in Oracle data
directories
If files are not converted, you can manually convert them using the Fork Translator
software.

Conversion is not possible when using VERITAS


Prinergy Administrator blocks protocol conversions if the VERITAS Storage
Replicator™ (VSR) software is installed on the Prinergy system. To determine
whether VERITAS is installed, check the Start menu on the primary server.
VERITAS, which is often part of a Hot Standby (EPM+) configuration of Prinergy,
uses a Windows operating system service that interferes with SMB, even when
the service is stopped. If you copy files from a computer running the Max OS X
to a primary or secondary server that is running the VERITAS service, the network
is interrupted and Prinergy stops responding. For information about the problem,
see the Microsoft Knowledge Base item "Server Randomly Drops All Connections,
System Log Records Multiple Instances of Event ID 2000," which is located at
http://support.Microsoft.com/kb/288301.
If you use VERITAS and you need to copy files to a primary or secondary server,
you must replace VERITAS with the DoubleTake software before you can convert
protocols. After removing VERITAS, you can convert protocols.
124 Chapter 7—Mac client computer protocols

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.

New volumes are not affected


If you add a new volume to the Prinergy system after you convert protocols, any
files on that volume will not contain resource information. If you want resources
for files on the new volume, you must manually convert the file resources using
the Fork Translator software.

Converting to SMB with AppleDouble


Use Prinergy Administrator to change the Mac-sharing protocol of
Prinergy and files on job volumes to SMB 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.

1. Close all files.


Open files will not be converted and, therefore, will not have resources.
Changing Mac client computer file-sharing protocols 125

2. Stop all archiving, purging, and retrieving activities:


● If you use the Prinergy Rules-Based Automation (RBA) software
and an enabled rule set uses the Archive/Retrieve JTP or Purge
JTP, stop Prinergy to prevent the rule sets from executing.
● If you do not stop Prinergy, stop the Archive/Retrieve JTP and
Purge JTP. They are located on either the Prinergy primary server
or a secondary server.

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

convert. For example, you do not need to convert a volume that is


used only for temporary storage or a volume that contains hot
folders or smart hot folders that accept input files and move them
to other locations.
● If a volume uses UNIX or Xserve, do not select it, because Prinergy
cannot convert them. If you select UNIX or Xserve volumes, you
create unnecessary and useless hidden files on the target volume.

7. Click Convert to SMB and click OK when prompted to confirm.


8. Wait until the conversion is complete.
As Prinergy counts the files on the volumes, the File Sharing dialog
box displays Converting. While Prinergy converts files, the dialog box
indicates how many files it has converted, such as 500 out of
estimated 10,000. The time that the conversion takes depends on
the number of files on the volumes.
When the conversion is complete, the following changes occur:
● Files on the selected volumes are converted to SMB.
● The File Sharing dialog box indicates how many files were
converted, such as Processed 10,000 out of 10,000. Files that do
not contain file resources are not processed, so the number of files
processed may not match the total number of files, even if there
are no errors.
● Prinergy is converted to SMB.

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

d. Use a Mac computer running Mac OS X to connect to the UNIX


volume via SMB.
e. Copy the files back to the UNIX volume, but place them in a
different folder.
If the files contain resource information, AppleDouble files 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. If you have a job volume on an Isilon server, disable ADS on each Isilon
share:
a. From a Windows client computer, connect to the Isilon share.
b. In the root folder, create a file named t.txt.
c. Open a command-prompt window, and change drives to the Isilon
share's root folder.
d. Run the following command:
ren t.txt .com.apple.smb.streams.off

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.

1. Close all files.


Open files will not be converted and, therefore, will not have resources.
2. Stop all archiving, purging, and retrieving activities:
● If you use the Prinergy Rules-Based Automation (RBA) software
and an enabled rule set uses the Archive/Retrieve JTP or Purge
JTP, stop Prinergy to prevent the rule sets from executing.
● If you do not stop Prinergy, stop the Archive/Retrieve JTP and
Purge JTP. They are located on either the Prinergy primary server
or a secondary server.
Changing Mac client computer file-sharing protocols 129

3. (Optional) If your system requires SFM, configure SFM on all Windows


servers in the Prinergy system.
4. (Optional) If you have a server that requires ExtremeZ-IP, install and
configure ExtremeZ-IP on all Windows servers in the Prinergy system.
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
convert. For example, you do not need to convert a volume that is
used only for temporary storage or a volume that contains hot
folders or smart hot folders that accept input files and move them
to other locations.
● If a volume uses UNIX or Xserve, do not select it, because Prinergy
cannot convert them. If you select UNIX or Xserve volumes, you
create unnecessary and useless hidden files on the target volume.

7. Click Convert to AFP and click OK when prompted to confirm.


8. Wait until the conversion is complete.
As Prinergy counts the files on the volumes, the File Sharing dialog
box displays Converting. While Prinergy converts files, the dialog box
indicates how many files it has converted, such as 500 out of
estimated 10,000. The time that the conversion takes depends on
the number of files on the volumes.
When the conversion is complete, the following changes occur:
● Files on the selected volumes are converted to SMB.
● The File Sharing dialog box indicates how many files were
converted, such as Processed 10,000 out of 10,000. Files that do
not contain file resources are not processed, so the number of files
processed may not match the total number of files, even if there
are no errors.
● Prinergy is converted to SMB.
130 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 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

Manually converting protocols


Manually change the Mac-sharing protocol of Prinergy and files on job
volumes to AFP or to SMB 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.
Only use this procedure if one of the following conditions apply:
● Your system includes the VERITAS Storage Replicator (VSR) software
or the VERITAS Replication Exec software, you are not able to replace
VERITAS with the Double-Take software, and you do not need to copy
files to the secondary server (because you store jobs only on tertiary
servers).
● Your system does not include any Windows job volumes, you want
to convert file sharing protocols without stopping the Prinergy system,
and you are converting between AFP and SMB with AppleDouble.

1. Close all files.


Open files will not be converted and, therefore, will not have resources.
2. Change a registry setting that switches between SMB and AFP in
Prinergy:
Important: If you are not familiar with using Registry Editor, contact
your service representative for help with editing the registry key. If
you use Registry Editor incorrectly, you can cause serious problems
that may require you to reinstall your operating system. Kodak does
not guarantee that problems caused by incorrect use of Registry Editor
can be resolved. Use Registry Editor at your own risk.
132 Chapter 7—Mac client computer protocols

a. In the registry of the Prinergy primary server, locate the


HKEY_LOCAL_MACHINE\SOFTWARE\Creo\Araxi\Set
tings\Default\System subkey.
b. Change the FileSystemConnectivityForOSXClient value. For SMB,
set it to 1. For AFP, set it to 2.
3. If you have a job volume on a Windows server, convert the files on it
with the Fork Translator software.
4. 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.
d. Use a Mac computer running Mac OS X to connect to the UNIX
volume via SMB.
e. Copy the files back to the UNIX volume, but place them in a
different folder.
If the files contain resource information, AppleDouble files are
created during the copying process.
f. Delete the original files.
5. 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.
6. If you have a job volume on an Isilon server, disable ADS on each Isilon
share:
a. From a Windows client computer, connect to the Isilon share.
b. In the root folder, create a file named t.txt.
Converting files with Fork Translator 133

c. Open a command-prompt window, and change drives to the Isilon


share's root folder.
d. Run the following command:
ren t.txt .com.apple.smb.streams.off

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

Converting files with Fork Translator


Manually run the Fork Translator utility to change resource information
for specific files or folders.
Requirements: All Prinergy server and client computers must be
successfully updated to Prinergy 3.1.0.7 or later.
Use Fork Translator to convert file resources in the following situations:
● You use special fonts, which are not converted by Prinergy
Administrator.
● Files were not converted by Prinergy Administrator because they were
open or had special characters or for other reasons.
● You must manually convert files—for example, because you use the
VERITAS software or you have an all-UNIX system.
● You want to restore files that were archived using NT Backup with a
different Mac client computer protocol.

1. Close all files that you want to convert.


2. On the Prinergy primary server or another Windows computer, open
a command-prompt window.
3. Enter the following command:
The complete syntax for the command is:
forktranslator {-a|-s|-h} [-i] [-n|-o] [-e] [-p] [-v]
pathname...

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.

4. Close the command-prompt window.

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

1. Click Start > Run, type regedit and click OK.


2. Navigate to My Computer > HKEY_LOCAL_MACHINE > SYSTEM >
CurrentControlSet > Services > AppleTalk > Parameters.
3. Right-click DesiredZone and select Modify.
4. In the Value data box, type * (asterisk) and click OK.
5. Close the Registry Editor window.
6. Right-click My Computer and select Manage.
7. In the Computer Management window, expand Services and Applications
and click Services.
8. In the right pane, right-click ExtremeZ-IP File and Print Server for Macintosh
and select Restart.
9. Close the Computer Management window.
136 Chapter 7—Mac client computer protocols
8 Proofing devices

About connecting Prinergy to Kodak Veris proofing devices, Kodak


Matchprint proofing devices, and third-party proofing devices.

Setting up a Kodak proofing device


Set up Kodak Veris and Matchprint proofing devices to work with the
Prinergy system.

Adding a Kodak proofing device


Add Kodak Veris and Matchprint proofing devices to the Prinergy system
manually.
The Kodak Veris and Matchprint proofing devices are controlled by the
Kodak Proofing Software on a separate server. With Kodak Proofing
Software, you can specify tiling flags and sheet templates that appear in
process templates in the Prinergy Workshop software.

1. Open Prinergy Administrator.


2. From the Tools menu, select Configure System.
3. In the Configuration Options dialog box, click the Kodak Proofers tab.
4. Click Add.
5. In the Add Kodak Proofer dialog box, either select a server from the
list or type the UNC path of the server that you want to add, in the
format \\servername\sharename
6. Click OK twice.
7. When a message warns you that you must restart the system, click
OK.
8. When you are ready, restart the Prinergy system on all servers.
When you add a Kodak proofing device manually to the Prinergy system, using
Prinergy Administrator, information from the proofing device appears in the
Device section of process templates in Prinergy Workshop.
138 Chapter 8—Proofing devices

Configuring a proofing device


After you connect a proofing device to the system, calibrate the color of
the device by generating test proofs and adjusting the calibration, until
you are satisfied with the results.
Requirements:
● JTPs are set up.
● The Kodak Harmony tonal calibration software is installed on the
appropriate Prinergy servers. Your service representative does this as
part of the Prinergy system installation.

1. In the Windows operating system, configure the default document


settings for the proofing device.
For information, see the operating system documentation.
2. Start Prinergy Workshop and generate an uncalibrated proof:
a. Create a loose page process template without any calibration
settings, because calibration settings are not available until you set
up the calibration curves in the Harmony software.
b. Generate a test file using the new process template.
c. Label the uncalibrated test proof so that you can compare it to
calibrated proofs that you generate later.
3. If desired, calibrate color for the proofing device using color calibration
software.
For information, see the documentation provided by the software
manufacturer.
4. In the Harmony software, set up calibration curves for the proofing
device.
Calibration curves are not available in process templates until you set
them up in the Harmony software. For information, see the Harmony
documentation.
5. For ink-jet proofing devices, set up an initial cut-back curve In the
Harmony software. If you do not, the proof will be overly saturated.
The curve can be adjusted later.
6. In Prinergy Workshop, generate a calibrated proof:
a. Create a loose page process template and set the calibration
settings.
b. Generate a test file using the new process template.
c. Label the calibrated test proof.
Setting up a third-party proofing device 139

7. Compare the calibrated proof to the uncalibrated one.


8. If necessary, adjust the calibration curves in the Harmony software,
adjust the process template, and generate proofs until you are satisfied
with the results.

Setting up a third-party proofing device


Set up a non-Kodak proofing device to work with the Prinergy system.

Supported third-party proofing devices


The Prinergy software handles many vector and raster output formats,
making it simple to connect to most proofing devices.
Prinergy can directly drive the Epson® 5000/7000/9000 printer series,
and any proofing device that accepts the HPRTL or Mutoh RTL raster
transfer languages. This includes wide-format proofing devices such as
the HP® 750, 1050, 2500, 5000, and 5500 printers.
Note: Only a subset of the RTL language is supported, and newer features
such as asymmetric resolutions are not supported.
Since printer manufacturers frequently update their printer languages,
Prinergy is not adding direct connections to other proofing devices.
Instead, Prinergy connects to most third-party (non-Kodak) proofing
devices using the proofing device's front-end RIP. Some proofing devices
use built-in RIPs and some use external RIPs.
For the connection to succeed, the proofing device must accept all the
file formats that Prinergy can output.
If your proofing device does not accept all the Prinergy output formats,
consider purchasing an external third-party front-end RIP, such as the
EFI® Best RIP, the CGS ORIS Color Tuner RIP, or the GMG ColorProof RIP.
For information, see the manufacturers' Web sites. Third-party RIPs
typically support a wide range of proofing devices and accept the
PostScript language, which ensures network connectivity.

See also:
Determining if a third-party proofing device can be used with Prinergy
on page 140
140 Chapter 8—Proofing devices

Determining if a third-party proofing device can be used with Prinergy


To determine whether a third-party proofing device can be used with
Prinergy, compare the file formats that the proofing device accepts with
the formats that Prinergy can output.
Requirements:
Obtain the user guide for the proofing device.

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.

2. Confirm that the proofing device can be physically connected to the


network.
Most proofing devices can be connected to the network either through
a built-in Ethernet port, using the TCP/IP protocol, or through a parallel
port on a host computer. You set up a print queue on the host computer
and connect it to the network using the TCP/IP protocol. For
instructions on setting up a print queue, refer to the documentation
for your computer's operating system.
Note: On some Hewlett Packard proofing devices, you may need to
purchase an HP JetDirect™ interface card or box for network
connectivity.

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.

4. After comparing the file formats:


● If the file formats match, your Prinergy software can drive the
proofing device. Drop a generic PostScript language file into the
Setting up a third-party proofing device 141

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

Configuring a proofing device


After you connect a proofing device to the system, calibrate the color of
the device by generating test proofs and adjusting the calibration, until
Setting up a third-party proofing device 143

you are satisfied with the results.


Requirements:
● JTPs are set up.
● The Kodak Harmony tonal calibration software is installed on the
appropriate Prinergy servers. Your service representative does this as
part of the Prinergy system installation.

1. In the Windows operating system, configure the default document


settings for the proofing device.
For information, see the operating system documentation.
2. Start Prinergy Workshop and generate an uncalibrated proof:
a. Create a loose page process template without any calibration
settings, because calibration settings are not available until you set
up the calibration curves in the Harmony software.
b. Generate a test file using the new process template.
c. Label the uncalibrated test proof so that you can compare it to
calibrated proofs that you generate later.
3. If desired, calibrate color for the proofing device using color calibration
software.
For information, see the documentation provided by the software
manufacturer.
4. In the Harmony software, set up calibration curves for the proofing
device.
Calibration curves are not available in process templates until you set
them up in the Harmony software. For information, see the Harmony
documentation.
5. For ink-jet proofing devices, set up an initial cut-back curve In the
Harmony software. If you do not, the proof will be overly saturated.
The curve can be adjusted later.
6. In Prinergy Workshop, generate a calibrated proof:
a. Create a loose page process template and set the calibration
settings.
b. Generate a test file using the new process template.
c. Label the calibrated test proof.
7. Compare the calibrated proof to the uncalibrated one.
8. If necessary, adjust the calibration curves in the Harmony software,
adjust the process template, and generate proofs until you are satisfied
with the results.
144 Chapter 8—Proofing devices
Adding output devices
Configure an output device so that Prinergy can send output to it.

Requirements: Ensure that:


● The output device is connected to a Prinergy server. For instructions,
see the server manufacturer's documentation.
● The output device's control software is installed on the Prinergy server
that is connected to the output device. For instructions, see the server
manufacturer's documentation or contact your service representative.
● The HiRes Render JTP has been added to the Prinergy server that is
connected to the output device.
● The Harmony software is installed on the appropriate Prinergy servers.
Your service representative does this as part of the Prinergy installation.

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

2. In the device control software:


a. Define the plate types to use with the Prinergy system.
See the documentation for the device control software.
b. Generate a PPD file and save it to the PPD folder on the Prinergy
server.
If you are using the Kodak Print Console software, generate the
PPD file in Landscape mode.
See the documentation for the device control software.

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.

Adding a digital printer


Add digital printers so that you can use them in Workshop.
Requirements:

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.

Changing a digital printer's file transfer protocol


Change a digital printer's file transfer protocol.
Requirements: Check with your IT department to see if you should be
using a specific file transfer protocol.

1. On the Managed Connections tab in the right pane, right-click a digital


printer and select Properties.
2. In the File Transfer list, select the file transfer protocol.
3. Click OK.
The other fields in the Properties dialog box are for information only
and cannot be modified.
148 Chapter 10—Digital printers

Removing a digital printer


Remove digital printers that you no longer need.

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.

Controlling who can use RBA


Give only specific users the right to manage RBA rules.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the User Rights tab.
3. Remove RBA rights for all users:
a. In the Users list, select EVERYONE.
b. In the Rights for list, clear the Manage Rule Sets check box.
4. Perform the following actions for each user who needs to work with
rule sets:
a. If the user does not appear in the Users list, click Add User, type
the person's Windows operating system user name, and click OK.
b. In the Users list, select the user.
c. In the Rights for list, select the Manage Rule Sets check box.
5. Click OK.
150 Chapter 11—RBA setup

Setting up e-mail service for RBA


Configure Administrator so that RBA can send e-mail messages using
your mail server.
Requirements:
● If you have InSite, you must first configure IIS and any firewall that
may exist on your system.
● You must know the following information about the mail server that
sends e-mail messages for your company:
❐ The mail server's name or IP address
❐ The mail server's SMTP port
❐ What type of authentication it uses

● If the server that is sending e-mail has McAfee® VirusScan® software,


configure the VirusScan software to allow AutomationApp.exe
to use port 25 to send outbound e-mail. For instructions, see the
McAfee documentation.

1. On the Prinergy primary server, in Administrator, from the Tools menu,


select Configure RBA.
2. In the Email Server box, type the name or IP address of the mail server.
3. If the mail server uses a port other than 25 for SMTP communication,
enter the port number in the Email Server Port box.
4. In the Login area, enter authentication settings:
● If the mail server allows anonymous connections, leave the
Authentication list set to Anonymous.
● If the mail server requires basic authentication, in the
Authentication list, select Basic (clear text), and complete the
Login area to identify the name and password of the authenticated
user account that RBA will use to send e-mail messages. Keep in
mind that basic authentication stores the user name and password
in the e-mail message as clear text, allowing hackers to detect the
user name and password as the message travels over the Internet.
● If the mail server requires Integrated Windows Authentication, in
the Authentication list, select NTLM. (NTLM stands for Windows
NT LAN Manager, the Microsoft Windows NT operating system
Challenge/Response authentication protocol.)

5. If you want RBA e-mail messages to be sent from a specific e-mail


address—rather than the default address automation@prinergy.com,
type the address in the Default Email Address box.
Handling rejected RBA e-mail messages 151

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.

7. Restart the Rule Engine daemon:


a. Open Windows Task Manager.
b. Click the Processes tab.
c. Click the Image Name column label to sort items alphabetically by
name.
d. Right-click WebServerApp.exe, and select End Process. Click
Yes to confirm.
e. Right-click AutomationApp.exe, and select End Process. Click
Yes to confirm.
In 30 seconds, the RBA engine restarts automatically.
8. Test the e-mail setup with an actual rule set.
For example, create a rule set in which the Manual Trigger event starts
the Email action that sends you a message.
For instructions on creating rules, see Workshop Help.

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.

Handling rejected RBA e-mail messages


If RBA e-mail messages are rejected, configure RBA to send e-mail
messages that include authentication information or from a different
e-mail address.
● If the mail server rejects messages because it requires authentication,
configure RBA to send the required authentication information in each
message. Some mail servers—especially those provided by a third
152 Chapter 11—RBA setup

party, such as an Internet Service Provider (ISP)—require


authentication to reduce e-mail spam.
● If the mail server rejects messages because it does not have an account
for the default RBA user, automation@Prinergy.com, you can change
the e-mail address from which RBA messages are sent. Change it to
the address of an authenticated user, such as the system administrator.
You can do this in either of the following ways:
● Change the default address of all RBA e-mail messages by setting
the Default Email Address box of the Configure RBA dialog box.
● Set the From parameter of each Email action in all RBA rules.

Preparing for RBA e-mail if you use InSite Prepress Portal


If your Prinergy system includes the Kodak InSite Prepress Portal system,
configure IIS and any firewall that may exist on your system so that RBA
can send e-mail messages.
If the Prepress Portal system is installed on a separate server, the Prepress
Portal server is the mail server. Otherwise, the Prinergy primary server is
the mail server.

1. On the Prepress Portal server, configure IIS to handle authentication:


a. From the Start menu, select Programs > Administrative Tools >
Internet Services Manager.
b. In the left pane, expand the server name.
c. Right-click Default SMTP Virtual Server, and select Properties.
d. Click the Access tab.
e. Click Authentication, and select one of the following check boxes:
Anonymous access, Basic authentication, or Integrated Windows
Authentication, which is the same as NTLM. (NTML stands for
the Windows NT LAN Manager, which is the Windows NT
Challenge/Response authentication protocol.)
2. If Prepress Portal is on a stand-alone server (not on the Prinergy
primary server), configure IIS on the Prepress Portal server to accept
and relay e-mail messages from the Prinergy primary server:
a. Click Connection, and click Add. In the IP address box, type the IP
address of the Prinergy primary server, and click OK twice.
b. Click Relay, and click Add. In the IP address box, type the IP
address of the Prinergy primary server, and click OK twice.
c. Click OK to close IIS.
Setting up file transfers for RBA 153

3. If Prepress Portal is not on the Prinergy primary server and there is a


firewall between it and the Prinergy primary server, open an SMTP
hole through the firewall from the Prinergy primary server to the
Prepress Portal server.
See the documentation for the firewall software.

Next:
You are now ready to set up e-mail service for RBA.

Setting up file transfers for RBA


Configure the File Transfer action and the Send Remote Trigger action
in RBA, including where the files are sent and on what port.

1. In Prinergy Administrator, from the Tools menu, select Configure


RBA.
2. Click the File Transfer tab.
3. In the Transfer Destination Path box, type or locate the folder where
Prinergy receives files that are transferred via RBA.
4. In the Transfer Metadata Path box, type the name of or locate the
folder where system files that track information about file transfers
(such as which files are included and how many bytes of each file were
sent) are stored.
5. In the Time until incomplete uploads are deleted box, type the number
of hours or days that you want Prinergy to keep files that were not
successfully transferred.
6. If you want to transfer files using a port other than 61236, type the
port number in the Port box.
7. If the Prinergy primary server has more than one network card, there
is a Multi-homed Server Only box on the File Transfer tab. Type the
IP address of the network card that will receive the files.
Typically, the IP address is visible to the sender or has a specific
bandwidth.
8. Click OK.
154 Chapter 11—RBA setup

Enabling client computers to use RBA


If client computers cannot access Rule Set Manager in Workshop, exclude
the Prinergy primary server from proxy settings.
In some cases, Workshop users cannot open Rule Set Manager. This
occurs primarily on Macintosh client computers, but it can also occur on
Windows client computers that use a proxy server.
● For Mac client computers, perform the following steps on each client
computer:
1. Double-click System Preferences, double-click Networks, click
Configure, and click the Proxies tab.
2. In Bypass proxy settings for these Hosts & Domains, type the IP
address of the Prinergy primary server, and click Apply Now.
Do not use the server name. You must use the IP address.
3. Restart the computer.

● 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

Selecting the default RIP for new jobs


Change the default RIP that all new jobs use and control whether it is
possible to generate a plate with a different RIP than the RIP used to
generate a proof.

1. From the Tools menu, select Configure System.


2. Click the Job Creation Defaults tab.
3. From the RIP Name list, select Adobe CPSI or 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.

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.

The signature ID code is applied to an imposition when it is imported into


a Prinergy job. When you create the imposed output, Prinergy replaces
the variable mark, sheet mark, or slug line with the actual code containing
information about that job.
Note: Use naming conventions for your jobs, impositions, and versions
so that signature ID codes are meaningful.

Defining the code syntax


In Administrator, customize the signature ID code syntax to fit the requirements
of your bindery equipment.
You can override the default signature ID code syntax by editing the Import
process template, saving it, and then importing the imposition using the updated
Import process template. These changes persist for subsequent uses of the
Import process template.
After it has been imported, the only way to alter the syntax is to re-import the
imposition using different settings. In a future release, you will be able to change
the syntax from within Workshop.
The syntax can use one or more of the following tags. None of the tags are
required. You can specify how many characters in the name tags to include in
the signature ID code.
● Prinergy job name (%jobname<n>%)
● Imposition name (%imposition<n>%)
● Version name (%version<n>%)
● Signature number (%signature<n>%)
● Total number of sections (%numsections%)
● Any number that is incremented by a value that you specify
158 Chapter 12—Preferences

Configuring the default signature ID code


Define the default signature ID code that will be applied to imported
impositions. You can override the default settings in Workshop in the
Import process template.
Requirements:
Both Workshop and Administrator must be running when you configure
signature ID codes.

1. From the Tools menu, select Configure System.


2. Click the Signature ID Code tab.
3. In the Code Template box, type the signature ID code in one line in
one of the following formats:
● %jobname<n>%%imposition<n>%%version<n>%%signa
ture<n>%%numsections%
Each tag must be enclosed with %. For example, %numsections%.
n is the number of characters to include, starting from the beginning
(left side) of the name or number. To include characters from the
end (right side) of the name or number, add a minus sign before
the number of characters, for example %jobname<-2>%.
● %n+m%
This is a simple incrementing signature ID code that prints a number
(n) on the first signature version and increments it by a specified
number (m) for each subsequent version.
For example %0000+1% prints 0000 on the first signature and
each subsequent signature version is incremented by 1.

Signature ID codes can be a mix of letters and numbers.


4. In the Number of Sections per Signature box, type the total number
of sections in each signature.
For example, if you import an imposition with five signatures and
signatures 2 and 5 each contains two sections, enter 1,2,1,1,2.
5. Click OK.
Examples
Configuring the default signature ID code 159

Description Context Signature ID codes # of Sections Resulting codes


per Signature
(type the signature ID
code in one line)

Simple incrementing Job name: 12345 %00001+1% 1 English signature 1:


number code 00001
# signatures: 2
(not available in English signature 2:
# sections per
4.0.2.1 release) 00002
signature: 1
French signature 1:
Versions: 01: English
00003
02: French
French signature 2:
00004

Versioned Job Job name: 12345 %jobname<-2>% 1 English signature 1:


450101
# signatures: 2 %Version<2>%
English signature 2:
#sections per %Signature<2>%
450102
signature: 1
French signature 1:
Versions: 01 -
450201
English and 02 -
French French signature 2:
450202

Multi-section job Job name: 0027 %jobname<-2>% 1,1,2,1,1 Signature 1: 27015


Text Section %signature<2>% Signature 2: 27025
# signatures: 5 %numsections% Signature 3: 27035
(signature 3 contains Signature 4: 27045
2 sections)
Signature 5: 27055

Pre-job (with %imposition<1>% 1 specific to the job


multiple (unique)
%version<-2>%
impositions)
%signature<2>%
160 Chapter 12—Preferences

Non-essential history entries


When processing a job, Prinergy generates detailed history entries to
allow you track actions performed on the job. The software considers
non-essential history entries to be less important.
You can configure Prinergy to delete non-essential history entries on a
regular basis—for example, every 30 days. In general, you should keep
other history entries indefinitely.
The Prinergy system considers the following history entries to be
non-essential:
● Element "a" submitted for processing: Indicates that a job or job
element has been submitted to the JTP for processing, but is not yet
queued at a particular JTP. For example, Page1 submitted at service
Normalize.
● Element "a" queued at service "b": Indicates that a job or job element
is queued for processing by a JTP. For example, Page1 queued at service
Normalize.
● Element "a" active at JTP "b": Indicates that a job or job element is
being processed. For example, Page1 active at service Normalize.
● Element "a" ended at JTP "b": Indicates that a job or job element is no
longer being processed, including when a task has been cancelled. For
example, Page1 stopped at service Normalize.
● Element "a" finished all processing: Indicates that a job or job element
has completed processing. For example, Page1 finished at service
Normalize.
● Assigned page "n" to page set "d"
● Trapping page "n" from file "x"
● Color-matching done on page "n" from file "x"
● Color-matching finished successfully
● Trapping finished successfully
● "n" traps created in "m" minutes
● No color-matching required, time in "m" minutes
● Page geometry assigned from the QuarkXPress® software registration
marks from file "x"
● Output device is beginning to plot the "n" separation
● No trapping required, time "m" minutes
● Output device has completed plotting the "n" separation
Controlling how long history logs are kept 161

● An unassigned page position has been selected for output. Assigning


a blank page as a substitute.
● Color-matching done on "n" objects in "m" minutes
● Warning and error messages from the RIP

See also:
Controlling how long history logs are kept on page 161
Compressing the database on page 220

Controlling how long history logs are kept


Control how long history entries and database reports are kept before
Prinergy deletes them.
Reducing the time Prinergy keeps history entries helps free disk space.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the History Logs tab.
3. Set the following options, entering a value between 7 and 99999 days:
Setting Specifies

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

Log all page


Include all page assignments and unassignments in the history
assignments
log.
to history
The default is off.
Note: This option causes your history log to increase in size
much faster.

Log all page


Include all page deletions in the history log.
deletions to
history The default is off.
Note: This option causes your history log to increase in size
much faster.

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.

Folders in a job folder


Each job has a main job folder that contains the following subfolders:

Subfolder Type of Information 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.

Hotfolders Hot folders, which you can configure hot folders.

Files that control job processing—for example the APA (Advanced Product Automation)
Control
file

Files that you've designated to be downloaded by InSite software users—for example,


WebDownLoads
font files or an ICC profile
Defining custom job folders 163

Subfolder Type of Information Stored

Files that have been uploaded by InSite software users—for example, software files or
WebUpLoads
graphics files for a job

Fonts Fonts that are used for the 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

Defining custom job folders


Define folders that Prinergy automatically creates each time a job is
created.
User-defined folders appear inside the UserDefinedFolders folder
of the job folder. These folders are generally used for storing input files.
A typical folders would be Source, Images, JobTickets, and so on.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Job Creation Defaults
tab.
3. Perform any of the following actions:
To Do This Do This

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.

Move a folder up Select the folder and click or .


or down in the list

Remove a folder Select the folder and click .

4. Click OK.
Changes you make affect new jobs only—not existing jobs.
164 Chapter 12—Preferences

Configuring the behavior of hot folders


Configure the group size, wait time between dropped files, and group
type for hot folders in the Prinergy system.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Hot Folders tab.
3. Set the following options:
Setting Specifies

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.

Controlling the error messages that Prinergy displays


Determine whether Prinergy displays warnings about server problems or
abnormally terminated processes.
● From the View menu, select one of the following options:
Setting Specifies

Notify Abnormal Prinergy will automatically notify you if a process or


Termination processes terminated abnormally.

Show Server Prinergy will automatically notify you of any server


Warnings warnings.
166 Chapter 12—Preferences

Configuring thumbnail compression and resolution


Determine the compression and resolution of thumbnails that Prinergy
generates and displays in Thumbnails view of Workshop.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Thumbnails tab.
3. Set the following options:
● JPEG Compression Quality: Enter a value between 1 and 100.
● Thumbnail Resolution: Enter a value between 1 and 300.

4. Click OK.
5. Stop and restart Prinergy.

Setting approval requirements


Identify whether to approve a InSite pages automatically, whether to
output unapproved pages, and set other job approval options.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Customer Approval
tab.
3. In the Web Jobs area, select the Auto-set web-enabled pages to
approval required option to make Prinergy automatically set a page's
job status to Approval Required when the page is refined in a
Web-enabled job.
Note: You can also set the status of pages to Approval Required from
the InSite software. Setting the page status in the InSite software
causes an e-mail notification to be sent to the customer's users,
indicating that pages are ready to be approved. If the page status is
automatically set in Prinergy, no e-mail notification is sent.

4. (Optional) In the Processing Control area, select any the following


check boxes:
● Allow overwrite of approved pages check box
● Only output surfaces or separations if all pages approved check
box
● Stop output if surface or separation contains rejected pages check
box
Displaying all IS screens in Process Template Editor 167

5. In the Scope of Output list, select one of the following options to


determine when the Only output surfaces or separations if all pages
approved check box and the Stop output if surface or separation
contains rejected pages check box will apply to jobs:
● Final Output only
● Imposed Proof and Final Output

6. In the Scope of Control list, select one of the following options to


determine the type of jobs to which the check boxes in the Process
Control area will apply:
● Apply to web-enabled jobs only
● Apply to all jobs

7. Click OK.
8. Stop and restart Prinergy.

Displaying all IS screens in Process Template Editor


Configure whether all IS screens are displayed in Process Template Editor
in Workshop.
IS screening is only available for high-resolution final output devices.

1. From the Tools menu, select Configure System.


2. Click the Screening tab.
3. Select Display all IS Screens, and click OK.
4. Restart all Prinergy servers.

Controlling revisioned pages for InSite


Control whether old revisions of page files remain in the job folder when
you generate new pages by re-refining input files.
You need old revisions of page files to compare pages in Kodak InSite
Prepress Portal 5.0 or later. If your system does not include the Prepress
Portal system, do not keep any revisioned pages.

1. From the Tools menu, select Configure System.


2. Click the Job Creation Defaults tab.
168 Chapter 12—Preferences

3. In the Max Revisioned Pages To Retain box, type a number that


indicates how many previous revisions you can view InSite Prepress
Portal.
With Prepress Portal, the recommended value is from 3 to 5.
Otherwise, the recommended value is 0. The maximum value is 99.
Important: Higher values consume more disk space because the job
folder stores multiple copies of page files.

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.

Example of keeping three previous revisions


For example, here's what happens when Max Revisioned
Pages to Retain is 3 and you repeatedly refine a one-page
input file named file.ps:

Refine Result

1st file.p1.pdf is generated

file.p1.pdf is renamed file.p1.rev1.pdf


2nd
file.p1.pdf is generated

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

name, and click .

Delete a Prinergy In the Dashboard Servers list, select a Prinergy server,


server
and click .

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)

Manages communications between the Media Manager,


Archive Daemon PArchiveD.exe
Windows RSM, and the Prinergy database.

Automation
PAutomationD.exe Manages workflow templates
Daemon

Sends and receives files from an Automation File Transfer


Automation File Server on another Prinergy server, when the Transfer
FileTransfer.exe
Transfer Server Files action is used in the Rules-Based Automation (RBA)
software

Hosts the Web services that provide an interface to RBA.


Automation Web
WebServerApp.exe Used by the Workshop software, the installer, RBA Status
Server
Web pages, and the Raise Event executables.

Client Manager
PClientManagerD.exe Manages the Workshop software connections
Daemon
172 Chapter 13—Monitoring

Full Name
(Application File Name (Filename column) Description
column)

Changes the database in response to changes in custom


Custom Field fields, including changes users make in Custom Field
PCustomFieldD.exe
Daemon Manager and Get Info dialog boxes, and extracts custom
fields from imposition imports

Receives job progress information from each Dashboard


Dashboard Collector Proxy Daemon it is connected to. Generates XML for
PDashCollectorD.exe
Daemon the Dashboard Web client to format for display to the
user.

A client computer process that collects job status


Dashboard Prinergy information from the database and forwards it to any
PDashProxyD.exe
Proxy Daemon Dashboard Collectors that have registered interest in a
set of jobs on that Prinergy system

Dashboard Web A small Web service that is based on a third-party


PDashWebServD.exe
Server Daemon product that enables Dashboard to run in a Web browser

Device & Service


PDeviceAndServiceD.exe Tracks the names and locations of JTPs
Daemon

DFE Manager Integrates a Digital Front End (DFE), such as the Prinergy
PDfeManagerD.exe
Daemon Evo software, into the Prinergy system

Diagnostics Log Maintains a log of all informational warning messages


PDiagnosticD.exe
Daemon and error messages for other daemons

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

Tests whether input files are visible to the server that a


File Daemon PFileD.exe
job is running on

General File
PFileSummaryD.exe Retrieves summary information for imposition plans
Summary Daemon

Monitors hot folders that are active on the server,


Hot Folder Daemon PHotFolderD.exe
including job hot folders and smart hot folders

Implementation Brokers requests to connect with daemons and maintains


Imr.exe
Repository Daemon a list of available daemons
Daemons 173

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

Enables the Workshop software to find the Prinergy


Locator Daemon PLocatorD.exe
system

Main Directory Maintains a listing of the secondary servers and jobs,


PMainDirectoryD.exe
Daemon and is responsible for user authentication at logon

Maintains a list of CORBA services. When a service is


Name Service NameServ.exe requested, it passes the service address to the client
computer.

Notification Server PNotificationServer.exe Notifies the Workshop software of changes on the server

Orbacus Notification Service, a third-party component


Notification Service NotServ.exe
involved in communication

Preflight Daemon PPreflightD.exe Provides PDF Preflight capabilities

Preps Integration Facilitates communication between the Preps software


PPrepsD.exe
Daemon and the Prinergy server

Bridges the Adobe Extreme technology with the rest of


Process Daemon PTaskD.exe
the Prinergy system

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)

Scans all Prinergy servers and the Prinergy database for


System Monitor free space. Issues a warning when space is below a
PSystemMonD.exe
Daemon certain threshold. Scans log files for errors and writes
the errors to the Prinergy Diagnostics window.

Thumbnail Daemon PThumbnailD.exe Generates thumbnails of arbitrary resolution

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.

1. In the right pane, click the Processes tab.


The Processes pane displays the following information:
Column Describes Possible Entries

Status of the process (indicated by


Green indicates the process is running.
the icon color)
Red indicates the process has stopped.

Application Name of process, suffixed with a


Processes include daemons and JTPs.
Windows operating system process
ID number—for example, Spool
Daemon (418).
Identifying Process IDs 175

Column Describes Possible Entries

Server Which server the process is running Any server name in your Prinergy system
on

Version Version number of the process


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.
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.

Status Status of the process


Running indicates the process is running on a server.
Ended indicates the process is not running on a server.
Terminated Abnormally indicates the process has
crashed or was stopped from NT Task Manager.

Filename Executable name of the process


Processes include daemons and JTPs.

2. If you want to sort processes by a different column, click the column


heading.
For example, if you want to sort the processes by file name, click the
Filename column.

Identifying Process IDs


Identify a Process ID (PID) so that you can troubleshoot, end a process,
trace the daemon stace, check memory usage, and so on.
● Find the process ID number in one of the following locations:
● In the Process pane, under the Application column
The name of the process is followed by the process ID number—for
example, Spool Daemon (418).
● In Windows Task Manager, under the PID column
176 Chapter 13—Monitoring
14 Database reports

With third-party reporting software, you can run reports that are built in
to Prinergy or create custom reports.

Running built-in reports


Run any of the built-in database reports by opening Crystal Reports and
connecting to the database on the primary server.
Requirements:
You must have the following software:
● Business Objects Crystal Reports software. Crystal Reports version 10
and later are supported. Version 9 and earlier are not supported
because they require an ODBC driver that does not support the date
format in Oracle 10.
● Oracle Instant Client software, which you can install by double-clicking
X:\\OracleClient_10.2.0\setup.exe on the Oracle DVD in
the Prinergy installation DVD set, where X is the letter of your
DVD-ROM drive
Important: Avoid running reports on the primary server because it reduces
the server's performance.

1. Start Crystal Reports, and select File > Open.


2. Open the %AraxiHome%\CreoAraxi\setup\Config\Sql\Re
porting folder on the primary server, select an .rpt file, and click
Open.
The reports opens in Design view in Crystal Reports.
3. Perform one of the following actions:
● Select View > Preview Sample, and then indicate how many records
you want to include.
● Select View > Print Preview.

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

5. In the Oracle Server dialog box, perform the following actions:


a. In the Service box, type server/AraxiDB, where server is the name
of the primary server.
b. In the User ID box and the Password box, type prinergy_rpt.
c. Click Finish.
6. If an ORA-12705 error appears, ensure that the computer where you
are running the reports has a language registry setting that matches
the setting on the primary server.
Important: If you are not familiar with using Registry Editor, contact
your service representative for help with editing the registry key. If
you use Registry Editor incorrectly, you can cause serious problems
that may require you to reinstall your operating system. Kodak does
not guarantee that problems caused by incorrect use of Registry Editor
can be resolved. Use Registry Editor at your own risk.
a. Open the registry of the primary server, locate the
\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE subkey, and
identify the value for NLS_LANG. For example, the value may be
AMERICAN_AMERICA.UTF8.
b. Open the registry of the client computer, locate the
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_ARAXI
subkey, and set NLS_LANG to the value of NLS_LANG on the
primary server.

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

Report title Description

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

Report title Description

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

Creating custom reports


Create custom reports by connecting third-party reporting software to
the database.
Requirements:
You must have:
● A license for Prinergy Custom Database Reporting (CDBR)
● Third-party reporting software, such as Business Objects Crystal
Reports. Crystal Reports version 10 and later are supported. Version
9 and earlier are not supported because they require an ODBC driver
that does not support the date format in Oracle 10.
● Oracle Instant Client software, which you can install by double-clicking
X:\\OracleClient_10.2.0\setup.exe on the Oracle DVD
in the Prinergy installation DVD set, where X is the letter of your
DVD-ROM drive
● Knowledge of relational databases and experience working with them
Creating custom reports 181

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.

1. On a client computer, start the Crystal Reports software, and create


a blank report.
Important: Avoid running reports on the primary server because it
reduces the server's performance.

2. In the Database Expert dialog box, click + next to Oracle Server.

3. In the Oracle Server dialog box, perform the following actions:


a. In the Service box, type server/AraxiDB, where server is the name
of the primary server.
b. In the User ID box and the Password box, type prinergy_rpt.
c. Click Finish.
4. If an ORA-12705 error appears, ensure that the computer where you
are running the reports has a language registry setting that matches
the setting on the primary server.
Important: If you are not familiar with using Registry Editor, contact
your service representative for help with editing the registry key. If
you use Registry Editor incorrectly, you can cause serious problems
that may require you to reinstall your operating system. Kodak does
not guarantee that problems caused by incorrect use of Registry Editor
can be resolved. Use Registry Editor at your own risk.
a. Open the registry of the primary server, locate the
\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE subkey, and
identify the value for NLS_LANG. For example, the value may be
AMERICAN_AMERICA.UTF8.
b. Open the registry of the client computer, locate the
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_ARAXI
subkey, and set NLS_LANG to the value of NLS_LANG on the
primary server.
182 Chapter 14—Database reports

5. Expand PRINERGY_RPT, and then expand Views.

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

Viewing database documentation


Read up-to-date documentation about the database so that you can create
custom reports.
Requirements:
You must have a license for Prinergy Custom Database Reporting (CDBR),
which provides read-only access to the Prinergy database so that you
can extract data for reporting and integration purposes.
CDBR uses database views, which are dynamic, virtual tables that provide
read-only access to the database. The CDBR views exactly match the
Interpreting history numbers 183

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.

1. On the primary server, in Windows Explorer, locate this folder:


%AraxiHome%\CreoAraxi\setup\Config\Sql\Cdbr
2. Double-click CDBR.htm.
The database documentation opens in a browser.

See also:
Creating custom reports on page 180
Interpreting history numbers on page 183
Character data in the database on page 184

Interpreting history numbers


To interpret history numbers in reports, look up the action description in
a properties file on the server.
You need to look up action descriptions because the database tables
store actions and action details as numbers, not as text.
Action descriptions are available only in English. They are translated into
other languages only when they appear in Workshop.

1. Get the number that identifies the action description:


● For actions, get the description from the HistLogActionNum column
in the DBCS_HistLogAction table.
● For action details, get the description from the HistLogDetailNum
column in the DBCS_HistLogDetail table.
For example, assume you look at a record in the DBCS_HistLogAction
table and find the number 1001 in the HistLogActionNum column.
2. Get the description that matches the number:
a. Open the %AraxiHome%\CreoAraxi\etc\hlog.proper
ties file on the primary server.
b. Search for the number.
The description is the text after the = symbol.
184 Chapter 14—Database reports

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

Character data in the database


When creating custom reports, you may want to know how the database
stores character data.
The database uses UTF-8 encoding for all character data, which requires:
● One byte for ASCII characters 0 to 127
● Up to two bytes for ASCII characters 128 to 255
● Three bytes for Unicode™ characters 256 to 65535
For more information about UTF-8, see
http://www.unicode.org/unicode/faq.
Variable-length character strings are stored in VARCHAR2 columns.
VARCHAR2 columns have a declared maximum length in bytes, not
number of characters. Therefore, it is difficult to infer a column's maximum
Character data in the database 185

string length in characters from a VARCHAR2 column's declared maximum


length.

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

What Archiver does


The Archiver system archives job files between Prinergy servers and tapes
or disk volumes.
The Archiver system performs the following main tasks:
● Archives files to store them on a tape or on a disk volume
The archive process copies all job files from a server to a tape or a disk
volume. Metadata about the job—that is, information about job data
and files linking together—remain in the database.
● Purges files to free disk space
The purge process verifies that job files were correctly archived and
then deletes the job files from the server. The job remains in Prinergy
because job metadata is retained in the database, including metadata
that indicate which files can be found on which tapes or disk volumes.
● Retrieves files from a tape or disk volume to restore a job
The retrieve process copies archived files from a tape or a disk volume
back to a server.

Tip: If you have Prinergy Rules-Based Automation (RBA), consider setting


up the Easy Archive rule to automate the archiving process. For
information, see the RBA Help.

How archiving and backup differ


An archive stores files in job context—that is, it includes all job files, even if they
are on multiple servers. For example, an archive can include input files from a file
server as well as the job folder on the job's home server. You typically save
archives indefinitely as a permanent record of jobs.
A backup does not store files in job context—that is, there is no relationship
between backup files and the database. A backup creates an image of a disk
partition, all or part of a file system, a system share, or the database files and
logs. You make backups for the purpose of disaster recovery—for example, a disk
crash or flood. You typically save backups only until the next backup.
188 Chapter 15—Archiving

Components of the Archiver system


The Archiver system includes several software and hardware components.
Archiver component What it is

Archiving station The Prinergy server that the Archiver


software runs on

Archive/Retrieve JTP Writes jobs or job files onto a tape or disk


volume, or returns archived files from a
tape or disk volume to the job's home
server. The process is controlled by the
Archive process template and the
Retrieve process template.

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.

Media Manager software Displays media pools in Prinergy


Workshop so that you view detailed
information about tapes and disk volumes
in those pools, including type, location,
amount of free space, and state. Also can
verify access, copy between tapes and
disk volumes, and set tapes to read-only
status.

Archive Disk Volumes Editor A tool in Prinergy Administrator that


allows you to add, modify, and remove
archive disk volumes

Removable storage media (for archiving Tapes where data is archived


to tape)

Removable storage devices (for archiving Tape libraries or tape drives that are
to tape) directly connected to the archiving
station

Removable Storage Manager (RSM) Tracks removable storage media and


software (for archiving to tape) manages removable storage devices,
such as an individual tape drive or tape
library.
Setting up the Archiver 189

Archiver component What it is

Microsoft Management Console (MMC) Hosts administrative tools (called MMC


software (for archiving to tape) snap-ins) that manage the hardware,
software, and network components of
the operating system. The Removable
Storage Manager is an MMC snap-in.
MMC and RSM are built into Windows
operating system.

Archiver Daemon (for archiving to tape) Manages communications between RSM,


the database, and Media Manager.

Setting up the Archiver


To use the Archiver system, you must add archiving JTPs and set up
archive, purge, and retrieve process templates.

1. In Administrator, on the archiving station, perform the following steps:


a. Add the Archive/Retrieve JTP.
b. Add the Disk Purge JTP.
2. In Workshop, create archive, purge, and retrieve process templates
that match your archiving strategy.
Important: When you create the archive process template, always
select more than one media pool. This creates a second copy of the
archive, which is similar to having a backup of important information
on your computer’s hard disk. If an archive tape or disk volume is
damaged, or an archive tape is lost, having a second copy of the archive
enables you to retrieve jobs that were stored on the tape or disk
volume.
Important: If you are using an archive process template that writes
archives to multiple media pools, you must create a corresponding
purge process template. The purge process template should specify
the same pools that are used in the archive process template. This
ensures that before purging a job or job files, the Archiver system will
verify that archives were successfully written to all pools. If you don’t
use a purge process template that specifies multiple pools, the Archiver
system will check only that each file has been archived to one media
pool, and you may accidentally purge a job before it has been
successfully archived to multiple pools.

See also:
Adding JTPs on page 30
190 Chapter 15—Archiving

Archiving to disk

About archiving to disk


You can archive job data to any disk volume on the network.
Archiving job data to a disk volume is generally faster than archiving to
tape, depending on the network speed. By archiving to disk, you eliminate
the risk of Removable Storage Manager database corruption, tape and
drive errors, and hardware problems.
Important: Make sure that you archive to two disk volumes and back up
each archive disk volume regularly.
After you set up an archive disk volume in Administrator, the disk volume
is available in Workshop in the same way as archive tapes:
● in the Archive dialog box, users can select disk volumes from the list
of available media pools
● in Media Manager, users can copy files between tapes and disk
volumes and verify that a disk volume is readable
● In Job Manager, jobs that are archived to disk appear on the Storage
and History tabs.
For more information about using archive disk volumes in Workshop, see
the Workshop help system.

Adding archive disk volumes


Add archive disk volumes so they are available for job storage in
Workshop.
Requirements:
● The Archive\Retrieve and Purge JTPs are set up.
● Archive, purge, and retrieve process templates are set up that match
your archiving strategy.
For more information, see Setting up the Archiver.

1. On the desired servers, share out two disk volumes.


Note: You should always archive to more than one disk volume.

2. In Administrator, stop the Archive\Retrieve and Purge JTPs: on the


JTPs tab, right-click the JTPs and select Stop JTP.
Modifying archive disk volumes 191

3. Select Tools > Archive Disk Volumes.


4. In the Archive Disk Volumes dialog box, select Add.
5. Type the UNC path (in the format \\servername\sharename).
You can also click Browse to navigate to the disk volume, and then
click OK.
6. Repeat steps 4 and 5 for any other disk volumes that you want to add.
7. Click OK.
Note: If you close the Add Archive Disk Volumes dialog box without
clicking OK, the disk volumes are not added.

8. Restart the Archive\Retrieve and Purge JTPs: on the JTPs tab,


right-click the JTPs and select Start JTP.

See also:
Setting up the Archiver on page 189

Modifying archive disk volumes


Replace an existing archive disk volume with a new archive disk volume.

1. In Administrator, stop the Archive\Retrieve and Purge JTPs: on the


JTPs tab, right-click the JTPs and select Stop JTP.
2. Select Tools > Archive Disk Volumes.
3. In the Archive Disk Volumes dialog box, select the disk volume and
click Modify.
You can also select multiple disk volumes to modify.
4. Type your user name and password.
Note: Any user can modify an archive disk volume, not just the
Administrator.

5. Type the UNC path (in the format \\servername\sharename).


You can also click Browse to navigate to the disk volume, and then
click OK.
You are reminded to copy the archived job files to the new disk volume.
To clear the Reminder dialog box, click OK.
6. Click OK.
Note: An entry is added to system history to record the name of the
user who modified the disk volume.
192 Chapter 15—Archiving

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

Removing archive disk volumes


Remove an existing archive disk volume.

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.

2. In Administrator, stop the Archive\Retrieve and Purge JTPs: on the


JTPs tab, right-click the JTPs and select Stop JTP.
3. Select Tools > Archive Disk Volumes.
4. In the Archive Disk Volumes dialog box, select the disk volume and
click Remove.
You can also select multiple disk volumes for removal.
5. Type your user name and password.
Note: Any user can remove an archive disk volume, not just the
Administrator.

6. Click OK.
Note: An entry is added to system history to record the name of the
user who removed the disk volume.

7. Restart the Archive\Retrieve and Purge JTPs: on the JTPs tab,


right-click the JTPs and select Start JTP.

See also:
Modifying archive disk volumes on page 191
Archiving to tape 193

Archiving to tape

Setting up removable storage devices


To set up removable storage devices, connect the devices and create
pools.
If you are using a removable storage device such as a tape library, you
must install the device and set up Archiver to link to the device.

1. Determine which attributes are most important for grouping


archives—for example, customer name, account/docket number,
month/year, publication, and so on.
2. Decide which Prinergy server you want to use as an archive station.
If you’re sharing a removable storage device with backup, you must
use the primary server as the archive station.
Important: Once you set up the Archiver system on a Prinergy server,
do not move the system. RSM stores contextual information about
tapes and media pools on the archiving station’s operating system.
Moving the Archiver system to another server could result in a loss
of this information, which may affect your ability to retrieve archived
jobs.

3. On the archiving station, install any necessary device drivers.


Check with your service representative to find out which versions of
the device drivers are required.
For information about installing device drivers, see the manufacturer’s
documentation.
4. Connect the removable storage devices to the archiving station.
For information about how to connect a device, see the manufacturer’s
documentation.
5. On the archiving station, use RSM to set up the application pools:
a. Select Start > Programs > Prinergy > Removable Storage
Management.
b. In RSM, create a pool called Archives.
c. Create pools that match your archiving strategy.
Important: Do not select the Return media to Free media pool option
on the General tab in the Create a New Media Pool Properties dialog
194 Chapter 15—Archiving

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.

Archiving job data to tape


The Archiver system works with Workshop to archive, purge, and retrieve
job data.
You can also copy tapes, verify tapes, and make a tape "complete" using
the Media Manager in Workshop. See Workshop Help.

1. In Workshop, start an archive process template on a job or on job files.


You can monitor the status of the process in Workshop. For
information about monitoring the process, see the Workshop Help.
2. If prompted, insert a tape.
The system can make the following requests:

Operator request Meaning


Please insert tape XXXNNN
An archive/retrieve request or task
into the library.
requires a tape that is offline.

Please insert a cleaning


A cleaning task is required for the drive.
cartridge into the library.

Prompts appear in the following places:


● As a prompt message on the archive station. The prompts do not
appear on other Prinergy servers.
● In RSM, in the Operator Requests folder
● As a Waiting for Operator Intervention icon in Workshop
Tip: If the Archiver system appears to be taking a long time to complete
a task, check these places to see if you must perform an operator
request before Archiver can proceed.
Important: To physically manage tapes, use RSM; do not use the
device's front panel to manually insert or eject tapes. If you do not use
RSM, it cannot track the tapes, and you will need to run a device
inventory.
Supported tapes and devices 195

3. If necessary, remove a tape from the drive and store it according to


your archiving strategy.
Important: If you are using an individual tape drive, Prinergy will write
consecutive archives, rather than simultaneous archives. The Archiver
system will prompt you to insert a new tape when the first archive is
complete. Prinergy cannot complete the second archive until you insert
the requested tape.
For information about viewing job or system history, see the Workshop
Help.
4. If desired, view historical information about archive, purge, and retrieve
jobs after the jobs are complete.
5. If RSM does not accurately reflect the contents of the tape drive, run
a device inventory. For example, an inventory is necessary if you used
the front panel controls on the removable storage device to eject a
tape.
a. In the console tree, double-click Physical Locations.
b. Right-click the library that you want to perform an inventory on,
and select Inventory.
Note: An inventory can be time consuming, particularly if you are using
a large tape library.

Supported tapes and devices


The Archiver system supports specific types of tapes and devices.

Tapes
Archiver supports MTF (Microsoft Tape Format) tapes, with the following
formats:
● AIT (Advanced Intelligent Tape)
Note: The WORM format is not supported.

● LTO™ (Linear Tape-Open) Ultrium™


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

In general, there are two types of tape 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.

Using devices for both archiving and backup


To save hardware costs, you can use the same removable storage device for
archiving and backup.
If you want to use the same device for archiving and backup, follow these
guidelines:
● Use the primary server as your archiving station, because the storage device
must be directly connected to the primary server.
● Use a tape library—not an individual tape drive—to minimize tape switching
and maximize performance.
● If your backups are automatic, devise a schedule that prevents backup and
archiving from occurring simultaneously.
● Distinguish the tapes by creating separate media pools for them, clearly
labeling them, and storing them separately.

Cleaning tape drives


Clean a drive if the drive indicates that cleaning is required (not just
recommended) or if the drive consistently gives read/write errors.
Important: In general, clean a drive only if required. Cleaning a drive too often
can produce unnecessary wear, shortening the drive life.
You must use a valid cleaning medium. The cleaning medium has a limited
life—for example, an AIT cleaning medium can be used approximately 70 times
before it becomes ineffective.
For information about cleaning a drive, see the RSM Help and the documentation
provided by the device’s manufacturer. For information about the cleaning
medium that you should use, see the tape manufacturer’s documentation.

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

Bar code systems


With a bar code system, you obtain bar codes from your tape manufacturer and
label tapes with preprinted bar coded labels.
Tape libraries come with a bar code reader that scans tapes and transmits the
information to RSM, which then assigns a name to the tapes based on the bar
code.
When ordering bar code labels, ensure that all bar codes are unique. To do this,
specify a different range of labels each time you add tapes to your system.

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.

Choosing a labeling method


If you have a tape library that reads bar codes, you must use a bar code system.
Even if you are using an individual tape device, it is best to use a bar code system
because:
● You can easily upgrade your existing archives, if you decide later to get a tape
library.
● You do not have to devise a naming strategy.
● You will never run out of names.
● It is much faster because each tape or disc does not have to be mounted to
read the on-tapes identifier.
198 Chapter 15—Archiving

Archive tape storage strategies


You can organize and store archive tapes in several ways, including by
month, location, and customer.
Storage strategy Pools Process templates Maintenance

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.

Considerations in selecting a strategy


An offsite strategy safeguards your data against an emergency such as fire or
theft.
The by-customer strategy is useful if your customers plan to supply and store
their own tapes. However, it is difficult to recycle tapes because archives are not
organized by date.
Removable Storage Manager 199

Removable Storage Manager


RSM displays information about archive and backup tapes, devices, and
activities.
Use Removable Storage Manager (RSM) to:
● Manage media pools
● Physically manipulate tapes in the device
● View history and status
● View tape locations and states
For information on using RSM, see the RSM Help, which is available from
the Help menu of RSM.

RSM views
View Displays

Media Pools Tapes by logical groupings, called pools


● Free: a built-in pool for blank, prepared tapes that you can write to
● Unrecognized: a built-in pool for tapes that RSM can't read
● Import: a built-in pool for tapes that are recognizable by RSM but new to this Prinergy system
● Application pools: user-defined pools for tapes that are used for archiving or backup. The pool
names vary, depending on the archiving strategy you use. Application pools appear in Workshop
in the archive, retrieve, and purge process templates.

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

What happens in RSM when you insert a tape


● If the tape was used before in this Prinergy system, RSM updates the location
of the tape.
200 Chapter 15—Archiving

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.

Moving a tape to the Free pool


When you move a tape to the Free pool, RSM performs the following steps to
prepare the tape:
● Permanently erases all data from the tape
● Changes the header to "free media label"
The most common reason to move a tape to the Free pool is when you insert a
new, blank tape and it appears in the Unrecognized pool.
You can also move a used tape to the Free pool when:
● The tape is in the Import pool, or the tape is in an application pool and it is
in the Available state.
● You want to erase the tape---that is, you no longer need any jobs on the tape.
● The jobs on the tape are destroyed in Prinergy. Otherwise, the jobs will appear
as archived and offline, even though the data is no longer available on the
tape and the job cannot be retrieved.

Monitoring the work queue


The following table describes the columns displayed in the Work Queue details
pane.
Archiving to tape 201

Column Description
name

State Current state of the task—for example, “Completed”


For a detailed description of possible task states, see the next table.

Operation Type of operation requested—for example, “Eject”

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.

Task state Description

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.

In Process The task is being processed.

Completed The task was completed successfully.

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

What backup does


Backup makes a portable copy of the database and system data for disaster
recovery.

Overview of the backup process


1. Create a backup of the database on a specific network location.
2. (Optional) Create a backup of your system files so that they are compressed
before you copy them to tape.
3. Copy the database backup and your system files to tape.
4. Run regular tests to make sure the data on the tape contains the files that you
need to restore the system.

How archiving and backup differ


An archive stores files in job context—that is, it includes all job files, even if they
are on multiple servers. For example, an archive can include input files from a file
server as well as the job folder on the job's home server. You typically save
archives indefinitely as a permanent record of jobs.
A backup does not store files in job context—that is, there is no relationship
between backup files and the database. A backup creates an image of a disk
partition, all or part of a file system, a system share, or the database files and
logs. You make backups for the purpose of disaster recovery—for example, a disk
crash or flood. You typically save backups only until the next backup.

Why backups are important


Backups are the best way to minimize data loss or damage caused by problems
such as:
● Disk failure
● Power outages
● Natural disasters, such as floods or earthquakes
● Virus infections
204 Chapter 16—Backup

Components of the backup system


A Prinergy backup system consists of several components, which are
determined by the backup software you use—for example, Prinergy Online
Backup.
Component Using Prinergy Online Using third-party software
Backup software

Software to Oracle Backup Manager


create a
database
backup file

Software to Prinergy Online Backup Third-party, Windows-compatible


back up files to software software
media
For example, Legato Networker or
Veritas BackupExec

Media Tapes Media of your choice

Devices A device qualified for Prinergy 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)

Backups with third-party software

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

When scheduling your backup, review the following considerations:


● A daily backup is the best way to ensure that you have the most up-to-date
data in the event of an emergency.
● If you use an individual tape drive and your backup spans more than one tape,
ensure that someone is on-site to insert new tapes.

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

❐ J:\oracle\oradata or g:\oracle\oradata, depending on the RAID drive letter

If your system has a single C: partition scheme, exclude the following folders:

❐ C:\oracle\oradata

❐ J:\oracle\oradata or g:\oracle\oradata, depending on the RAID drive letter

If you have any questions, contact your service representative.

● Windows system state


● Folder that contains the major update uninstall files (usually E\PrinergyUpdates)
● Windows system state

Tertiary You do not have to back up these servers, because:


servers and
● The data is not required for system recovery.
file servers
● The backups will take a long time, which taxes your system unnecessarily and reduces productivity.
● The backups will consume significant media space, which increases the risk of running out of
media during a backup.
● Job data should be archived, rather than included in backups. If you want to back up your jobs,
you may be able to use Windows Backup or other third-party software for a separate backup
operation. You are responsible for configuring and maintaining this software and associated
backups.
Configuring backups with third-party software 207

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.

Configuring backups with third-party software


If you use third-party software for backups, configure Oracle Backup
Manager and your third-party software.
Requirements:
Provide your own backup software and removable storage device.
Use this procedure only if you are using third-party software for backups.

1. Develop a backup plan.


2. Connect the removable storage device that you will use for backup.
For information about connecting your device, see the manufacturer’s
documentation.
3. Configure Oracle Backup Manager to back up your database to a local
disk at a regularly scheduled time, as determined in your backup plan.
a. Open a command-prompt window, type ORACLEBACKUPMANAGER,
and press Enter.
The Araxi_OracleMgr> prompt appears.
b. Type SHOW BACKUPCONFIG and press Enter.
c. Set the parameters that you want to change:
To specify this Enter this

ALTER BACKUP_START_HOUR = <integer from 0 to 22>


The hour of the day that a The default value is 3 (3 a.m.). Choose the least busy time, but choose a time
scheduled backup starts when staff are on-site to change a tape if required. The value 23 (11 p.m.) is
reserved for the Oracle Backup Manager scheduler.

The frequency (in days) ALTER FULL_BACKUP_INTERVAL = <integer>


between full backups The recommended value is 0 (daily).

Whether Prinergy shuts down ALTER SHUTDOWN_TO_BACKUP = <YES or NO>


during backup The recommended value is NO.
208 Chapter 16—Backup

To specify this Enter this

The folder where files are ALTER BACKUP_DESTINATION = <path>


stored temporarily during the The default setting is <data_log_drive>\ORACLEBACKUP. If the E drive
backup process lacks space, you can use the RAID.

The folder for the final backup ALTER ZIP_FILES_DESTINATION = <path>


files (in .ZIP format) The default setting is <data_log_drive>\ORACLEBACKUP.

How long (in seconds) to wait ALTER BACKUP_SUCCESS_COMMAND_WARNING = <integer>


for a success message before
generating a warning The default value is 3600 seconds (one hour).

Note: Leave the INCR_BACKUP_INTERVAL parameter set to 0


because incremental backups are not recommended.

4. At the Araxi_OracleMgr> prompt, type BACKUP START and press Enter


to turn on the scheduler for Oracle Backup Manager.
Tip: To stop the scheduler, type BACKUP STOP and press Enter.

5. Install and configure your backup software to automatically copy the


database backup to media and to back up the system drives of your
Prinergy servers to media.
6. Prepare and allocate media.

Performing a backup with third-party software


Back up your system with this procedure only if you use third-party
software for backups.

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

3. If you want to trigger a backup immediately, perform the following


steps:
a. Open a command-prompt window, type ORACLEBACKUPMANAGER,
and press Enter.
The Araxi_OracleMgr> prompt appears.
b. Type BACKUP DATABASE and press Enter.
4. If required, insert a new tape.
A new tape is required if you use an individual tape drive and the data
does not fit on one tape.
5. When the backup is finished, store the backup tape according to your
backup plan.
If you use an individual tape drive and alternate between two tapes,
remove the tapes from the device and insert the next day’s tape.

Prinergy Online Backup option

Prinergy Online Backup


Prinergy Online Backup includes Oracle Backup Manager and Prinergy
Backup software.
The Oracle Backup Manager software performs a daily backup of the
Oracle database to a local disk. The Prinergy Backup software writes the
backup of the Oracle database to tape or disk and backs up system drives
of the Prinergy primary and secondary servers to tape or disk.

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.

Allocating tapes for backup


If you use Prinergy Online Backup on Windows Server 2003, allocate
tapes to the backup.
Requirements:
Prepare the tapes you need for the backup.
Use this procedure only if you are using Prinergy Online Backup on
Windows Server 2003. When you start Windows NT Backup under
Windows 2003, the tapes in the Backup pools are returned to the Free
pool, causing the Prinergy backup to fail.
If you are using Prinergy Online Backup on Windows 2000, the Prinergy
Backup software automatically creates the necessary media pools for
managing a backup.

1. On the primary server, open a command-prompt window, type


ntbackup, and press Enter.
If a Backup or Restore Wizard dialog box appears, click Advanced
Mode in the dialog box.
2. Keep the Backup Utility window open.
3. From the Start menu, select Administrative Tools > Computer
Management.
4. In the Computer Management window, locate Storage > Removable
Storage > Media Pools > Backup > Prinergy.
5. If necessary, create the Backup pool and the Prinergy subpool.
a. Right-click Media Pools and select Create Media Pool.
b. In the Name box, type Backup.
Configuring backups with Prinergy Online Backup 211

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:

Name box Prinergy

Media information box Select Contains media of type, and then specify
the type of media you use:
● 8 mm AIT1
● LTO Ultrium

Allocation / Deallocation Select the following options:


policy box
● Draw media from Free media pool
● Return media to Free media pool

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.

Configuring backups with Prinergy Online Backup


If you use Prinergy Online Backup, define the servers that will be backed
up and the location where the backup is created.
This procedure applies only if you are using the Prinergy Online Backup
software.
212 Chapter 16—Backup

You can add Prinergy secondary servers, render stations, and the InSite
software Web servers to the list. You cannot add tertiary servers.

1. From the Tools menu, select Configure System.


2. In the Configuration Options dialog box, click the Backup tab.
3. If you want to back up a server that is not in the list, add a server to
the list.
a. Click Add Server.
The only servers that you can add are Prinergy secondary servers,
Prinergy render stations, and InSite Web servers. You cannot add
a tertiary server.
b. In the Backup Medium list, select the medium on which to back up
the files. You can back up to a tape or to a file.
c. If you selected FILE in the Backup Medium list, click Browse to
select a location for the backup on the shared folder.
d. (Optional for backup to tape only) Select the Override Default
Compression Setting check box to override the default compression
setting of the hardware device that you use for system backup, and
then select Enable Compression or Disable Compression.
4. If you want to stop backing up a server, select the server that you want
to remove from the list, click Remove Server, and confirm that you
want to remove the server.
5. Click OK.

Performing a backup with Prinergy Online Backup


Back up your system with this procedure only if you use Prinergy Online
Backup.
Once your system is configured for backup, your main responsibilities
are to ensure that the backups are successfully completed as scheduled
and that backup media are handled and stored according to your strategy.

1. Ensure that the appropriate backup medium is online—that is, the


medium designated for use according to your media rotation strategy.
If you use a tape library, you may also want to ensure that media are
available in the Free pool. This enables RSM to draw additional media
if necessary. If not enough media are available, the backup will fail.
2. Wait for the backup to occur automatically.
Monitoring database backups 213

3. In Administrator, confirm that the backup was successful by performing


one of the following steps:
● Check the backup status box in the lower-left corner of the Prinergy
Administrator window.
● From the Tools menu, select System Backup to open a dialog box
that lists details about the backup status.
Important: Your system is configured to automatically confirm whether
the backup was successful after a specified interval—usually eight
hours. Prinergy Administrator displays the correct backup status only
after the system completes the confirmation. If you check the backup
status before the confirmation is finished, the information displayed
reflects the status of the previous backup.

4. When the backup is finished, store the backup media according to


your backup plan.
If you use an individual tape drive and alternate between two tapes,
remove the tape from the device when the backup is finished and
insert the next day’s medium. If you use a tape library, ensure that
tapes are available in the Free pool. For instructions on using RSM to
move media to the Free pool, see the RSM Help.

Monitoring database backups


If you use third-party software for backups, view the success of database
backups.
Use this procedure only if you use third-party software for backups. If
you use Prinergy Online Backup, you can see backup history in
Administrator.

1. Use Oracle Backup Manager to view backup history.


a. Open a command-prompt window, and type ORACLEBACKUPMANAGER.
The Araxi_OracleMgr> prompt appears.
b. Type SHOW BACKUPTIMES.
c. Type EXIT.
2. View the log file:
<data_log_drive>:\<OracleFolder>\Creo\Logs\Ora
cleBackupLogFile.log
214 Chapter 16—Backup

What to do if a backup fails


If a backup fails, try to identify the cause. If the problem persists, call your
service representative.

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.

Media rotation strategies


Select a strategy for rotating the media that you use to back up your
system.

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.

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

Tape1 Tape2 Tape1 Tape2 Tape1 Tape2 Tape1

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

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

Tape1 Tape2 Tape3 Tape4 Tape5 Tape6 Tape7

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.

Week Monday Tuesday Wednesday Thursday Friday Saturday Sunday

Week 1, 3, Tape1 Tape2 Tape3 Tape4 Tape5 Tape6 Tape7


5...

Week 2, 4, Tape8 Tape9 Tape10 Tape11 Tape12 Tape13 Tape14


6...

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 and devices supported for backup


Prinergy backup supports specific types of media and devices.

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.

Using devices for both archiving and backup


To save hardware costs, you can use the same removable storage device for
archiving and backup.
If you want to use the same device for archiving and backup, follow these
guidelines:
● Use the primary server as your archiving station, because the storage device
must be directly connected to the primary server.
● Use a tape library—not an individual tape drive—to minimize tape switching
and maximize performance.
● If your backups are automatic, devise a schedule that prevents backup and
archiving from occurring simultaneously.
● Distinguish the tapes by creating separate media pools for them, clearly
labeling them, and storing them separately.

Cleaning tape drives


Clean a drive if the drive indicates that cleaning is required (not just
recommended) or if the drive consistently gives read/write errors.
Important: In general, clean a drive only if required. Cleaning a drive too often
can produce unnecessary wear, shortening the drive life.
You must use a valid cleaning medium. The cleaning medium has a limited
life—for example, an AIT cleaning medium can be used approximately 70 times
before it becomes ineffective.
For information about cleaning a drive, see the RSM Help and the documentation
provided by the device’s manufacturer. For information about the cleaning
medium that you should use, see the tape manufacturer’s documentation.
17 Maintenance

These are guidelines that you can use to keep your Prinergy system running
in optimum condition, minimize down time, and improve system stability.

Performing daily maintenance tasks


Perform these maintenance tasks daily to keep your Prinergy system
running in optimum condition.

1. Check your Prinergy system backup:


a. Start Prinergy Administrator on the primary server.
b. From the Tools menu, select System Backup Status.
2. If applicable, check your data backup.
3. Visually check hardware such as servers, RAIDs, or other peripherals
and report any error conditions, for example, amber-colored LEDs.

Performing weekly maintenance tasks


Perform these maintenance tasks every week to keep your Prinergy system
running in optimum condition.

1. Execute a full restart of all Prinergy servers:


a. Start Prinergy Administrator on the primary server.
b. From the File menu, select Stop, then select All Servers and click
Stop to stop Prinergy.
c. When the Prinergy software is stopped, restart all Prinergy server
computers.
d. Log on to Microsoft Windows when the servers are restarted.
e. Start Prinergy Administrator on the primary server, and from the
File menu, select Start to start Prinergy.
2. Check the RAID and other volumes for free space. Ensure each volume
has a minimum of 20% free space.
3. Check the RAID and other volumes for fragmentation. Defragment if
the fragmentation is more than 20%.
You can use the PerfectDisk program to defragment. See the eCentral®
portal for a white paper on this program. The eCentral portal is at
218 Chapter 17—Maintenance

https://ecentral.kodak.com/. Search for "PerfectDisk' or


"Defragmentation".
4. Check and update virus definitions. Verify that all systems are scanned
for viruses and worms.
See the eCentral portal for more information about using and installing
Norton Antivirus on Prinergy systems. The eCentral portal is at
https://ecentral.kodak.com/. Search for "Antivirus".
5. Check and apply only Prinergy-approved Microsoft Windows security
updates and hot fixes.
See the eCentral portal for more information about Microsoft security
updates and hot fixes. The eCentral portal is at
https://ecentral.kodak.com/. Search for "Antivirus".

Performing monthly maintenance tasks


Perform these maintenance tasks monthly to keep your Prinergy system
running in optimum condition.

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.

Freeing disk space


If the system reports that the amount of disk space is below the threshold,
try to free some disk space on the system.

1. Remove obsolete snapshot information. A snapshot can be considered


obsolete if the system has been running successfully on the current
software version for several weeks and there are no chances of the
system being rolled back. The snapshot information can be found in
the PrinergySnapshotInformation folder that is normally
located on drive E or the drive you specified during your upgrade. You
can delete the entire folder.
2. Compress the database.
3. Archive and purge completed jobs.
4. If there is a memory.dmp file in the the Winnt folder, delete that file.
Freeing disk space 219

5. If there is a user.dmp file in the \Documents and Set


tings\All Users\Documents\DrWatson folder, delete that
file.
6. Move the NT print spool folder to another drive. In Settings > Printers
> File > Server Properties > Advanced, change the spool folder
location to drive E or J.
7. Delete downloaded and installed Prinergy updates (or move them to
another volume) after installing.
8. If your Prinergy system has been running at a certain version for several
months, you can delete the files used to install older updates. For
instance, after running 3.x for a few months, you could remove the
files that were used to install 2.3, as it is unlikely you will need to roll
back to the old version. These files are stored in D:\Priner
gy2.0.4\CreoAraxi\support\patches\in
stalled_Prinergy.

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

Compressing the database


Compress the Oracle database to reduce the amount of disk space that
the database uses.
Requirements:
Important: If you are using Prinergy version 3.1.0.5 or earlier, do not
compress the database or you might have problems upgrading to Prinergy
version 4.
Schedule the compression, considering the following factors:
● The need to stop the Prinergy system. You can compress the database
only when the Prinergy system is not running.
● The time it will take, which depends on the size of the database and
the speed of the Prinergy primary server. For example, if the database
is very large, compression can take several hours.
● How frequently it needs to be done. Compress the database
regularly—for example, every three to six months. The frequency
depends on how active your site is.

1. Quit the Prinergy Workshop software on all client computers.


2. Stop Prinergy on all servers.
3. Shut down and restart the Prinergy primary server to ensure that the
database is not in the process of being backed up.
4. Start Prinergy Administrator.
5. In Prinergy Administrator, from the Tools menu, select Compress
Database.
The Compress Database menu item is available only on the Prinergy
primary server, and only when Prinergy is not running.
6. In the Compress Database dialog box, click Compress.
Database compression starts. The following table describes the
information that appears as compression proceeds.
Item Description

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

Size The size of the internal database object currently being


compressed. Compression starts at the largest database object
and proceeds to the smallest database object.
Disk clean-up tool 221

Item Description

Elapsed time The amount of time it has taken so far to compress the database
object identified in Name

Status The task currently underway—for example, "Compressing x of


y", where x is the database object being compressed and y is
the total number of database objects

Total The total amount of time since Compress was pressed


compression
time

7. When the "Database compression completed" message appears, close


the Compression dialog box.
Note: If you cancel the compression process before it is complete,
Prinergy will take longer to start up because the database index must
be rebuilt.
Note: If the compression software terminates abnormally, restart your
system, and then restart the compression. The compression process
will resume where it left off.

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.

Disk clean-up tool


This tool performs disk management tasks on the Prinergy system,
including deleting unneeded files.
The Prinergy Disk Cleanup Tool allows system administrators to perform
the following maintenance tasks on their Prinergy system:
222 Chapter 17—Maintenance

● View a list of files that can be removed.


● Delete old log files, temporary files, and previous Prinergy updates.
● Move the page file to a drive with available space.
● Move the spool folder for a printer to a different drive.
● Change the locations of folders that Prinergy manages, such as the
TaskServerData folder.
This tool frees up space on Prinergy system drives, maintains good system
performance, and makes it easier to install Prinergy updates. It is available
on the primary server at Start > Kodak > Prinergy Support Tools >
Prinergy Disk Cleanup Tool.
18 Prinergy updates

Download and install updates and upgrades to Prinergy software.

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/ .

Updating Prinergy software


When an update is available for your Prinergy software, download it from
the eCentral portal and install it.

1. Log on to the https://ecentral.kodak.com/ portal, select Self-Support >


Downloads, select Prinergy, and click OK.
Note: Visit the eCentral portal regularly for Prinergy downloads and
documentation. If you are not yet a registered user of the eCentral
portal, you can register online at https://ecentral.kodak.com/.
224 Chapter 18—Prinergy updates

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.

5. Stop Prinergy on the primary server.


6. Stop Prinergy on all the secondary servers and render stations.
7. In the Temp folder on the primary server, double-click PUpdate.exe.
8. In the Prinergy Update Utility, follow the prompts.
When the installation is complete, a Success screen appears.
9. Click Exit.
10. Repeat Steps 7 to 9 on each secondary server and render station that
you want to update.
11. After all the servers are successfully updated, start Prinergy on the
primary server.
12. Start Prinergy on the secondary servers and render stations.
13. On each client computer, start Prinergy Workshop. In the Workshop
Login dialog box, type the name of the primary server and click Login.
If the Synchronize Workshop message appears, click Yes.
Note: Some updates do not affect Prinergy Workshop, so the
Synchronize Workshop message may not appear.

Deleting the Prinergy 3.x database


Two or more weeks after you upgrade to Prinergy 4.x, you need to delete
the Prinergy 3.x database to free disk space on the Prinergy primary server
and on secondary servers configured with Hot Standby (EPM+).
Requirements:
Wait for a message to appear on the Prinergy primary server advising
you to delete the Prinergy 3.x database. Until it appears and you click it,
the Delete Prinergy 3 Database menu item is not visible. The message
appears about two weeks after you upgrade to Prinergy 4.x.
Deleting the database takes only about 5 to 10 minutes. It requires that
you stop Prinergy first.
Deleting the Prinergy 3.x database 225

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

Multiple Prinergy systems


When you have more than one Prinergy system, you can use Administrator
software remotely but you cannot share secondary servers.

Using Administrator software remotely


You can use Administrator software on one primary server to connect to the
Admnistrator software on another primary server.

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.

Using Prinergy Dashboard to view jobs on multiple Prinergy


servers
Prinergy Dashboard can show the status and progress of jobs on multiple Prinergy
servers. You can set up Dashboard to view job status on multiple Prinergy servers.

See also:
Administering Dashboard on page 169

Prinergy across a WAN


It is possible to use Prinergy across a WAN, but performance is generally
slower and less reliable and the Kodak service contract does not cover
WAN-related problems.
Important: Although Prinergy and other Kodak software have been tested
across a Wide Area Network (WAN), Kodak does not support, and
assumes no responsibility for, problems that may occur as a result of using
a WAN. WAN-related problems are not covered by Kodak service
contracts. However, Kodak offers fee-based Network Consulting Services
for custom network troubleshooting and performance tuning. For further
information, contact your service representative.
228 Chapter 19—Large systems

A WAN is usually composed of two or more Local Area Networks (LANs)


joined by one or more connectivity technologies (xDSL, T1-3, ATM,
OC-xxx, frame relay, ISDN, x.25, and so on).
It is possible to use a Prinergy system across a WAN in the following
ways:
● To connect Prinergy Workshop to the Prinergy primary server located
at another site (that is, at a different geographic location)
● To connect the Prinergy primary server at one site to a render station
and output device at another site
Note: In this configuration, Emergency Platemaking is strongly
recommended, so that the remote render station can still be used to
output plates if the WAN connection is temporarily unavailable (if the
data can be sent by an alternate channel).

Note the following requirements for using Prinergy across a WAN:


● Bandwidth must be at least 100 Mbps for platemaking across a WAN.
Slower WANs might be unable to provide adequate performance for
a Prinergy workflow. If you are only using Prinergy Workshop, the
bandwidth requirement is 10 Mbps.
● Ability to route all protocols required by Prinergy across the WAN
(TCP/IP and AppleTalk)
● Ports required for communication between Prinergy servers (or
between Prinergy and InSite) must not be blocked. This is rarely a
problem for private networks.
● Guaranteed packet delivery, which precludes the use of frame relays
with Prinergy
● Low latency. Satellite link latency is usually too high to use with
Prinergy. A high WAN latency may cause Prinergy components to fail
while waiting for data, leading to unpredictable behavior.
Kodak cannot predict Prinergy performance across a WAN. Generally,
unless your WAN has extremely high bandwidth, you can expect much
slower performance than an Ethernet connection.
Kodak tested platemaking with Prinergy using a 30 Mbps WAN between
two sites. Performance was adequate for Workshop use but was
inadequate for platemaking. To make plates at a remote site, 100 Mbps
or faster bandwidth is required.
The impact of a WAN becoming unavailable and interrupting production
is approximately the same as the impact of a LAN failure. As a rule, all
mission-critical networks should be as reliable as possible. However, if a
WAN fails, it may be more difficult to secure an alternate connection. If
a LAN switch is faulty, you may be able to replace it with a spare switch
Connecting to Administrator on another server 229

or run a cable between two servers to restore production. This kind of


quick solution is not possible if servers are in different geographical
locations and the switch/router is in a different location as well.

Connecting to Administrator on another server


Use Administrator software on one primary server to connect to the
Administrator software on another primary or secondary server.
This is useful when you are working on one Prinergy system and you want
to start or stop a server in another Prinergy system without moving to
the other Prinergy system.

1. From the File menu, select Connect to Server.


2. In the Enter the name of the Prinergy server box, enter a server name
(for example, Secondary).
3. In the Logon As box, type your user name and password.
Note: You must log on with an account that has administrator
privileges.

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

composed of cyan and yellow, so cyan and yellow can be considered


colorants that make up the color green.

color database
A database that contains information about spot colors—for example,
process color recipes and ink parameters necessary for trapping.

color match (verb)


To keep colors consistent when converting one color space to another—for
example, RGB to CMYK.

Common Object Request Broker Architecture (CORBA)


A standard that allows applications to communicate with one another
regardless of their operating system or hardware. Prinergy Evo software
uses CORBA for some internal communications.

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 linear tape (DLT)


A high-capacity media for general data storage, archival, or system
backup. It is also suitable for near-on-line storage and catalogued retrieval
of large files and large sequential data sets.

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.

JDF (Job Definition Format)


An XML-based file format and proposed industry standard for end-to-end
job ticket specifications. It is combined with a message description
standard and message interchange protocol. JDF is designed to streamline
information exchange between different software and systems. It is
235

intended to supply a way for printing businesses to streamline the process


of producing printed material.

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.

job ticket processor (JTP)


The software that performs a specific processing step to help process a
job ticket.

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.

loose page proof


The output of a refined page or pages to a proofer (such as a laser printer
or color printer), or to a Prinergy Virtual Proofing System proof.

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.

NCT file format


A CT file format that supports spot colors.
237

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.

page set position


A number that identifies where a page will be assigned in a page set.

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

PJTF (Portable Job Ticket Format)


An imposition file that contains descriptions of device-specific settings
and describes the desired output style for one or more pages from PDF
files.
238 Chapter 20—Glossary

portable job ticket format

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

SMB (Server Message Block)


SMB, also known as CIFS (Common Internet File System), is a protocol for
sharing files, printers, and other resources between computers.

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.