SysAdminGuide

Prinergy

Workflow System

Version 5.0

System Administration Guide

English

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

3

System overview

2

Distributing the system...9

Web browser access...10

Installation folder (%AraxiHome%) ...11

13

Licenses

3

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

25

JTPs

4

Changing an existing JTP pool...38

41

Users

5

User accounts...41

Configuring users in a domain...42

Configuring users in a workgroup...43

Setting user rights...44

47

Servers

6

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

107

Mac client computer protocols

7

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

Prinergy vi

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

137

Proofing devices

8

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

145

Adding output devices

9

147

Digital printers

10

Changing a digital printer's file transfer protocol...147

Removing a digital printer...148

149

RBA setup

11

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

155

Preferences

12

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

vii Contents

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

171

Monitoring

13

Identifying Process IDs...175

177

Database reports

14

Built-in reports...178

Creating custom reports...180

Viewing database documentation...182

Interpreting history numbers...183

Character data in the database...184

187

Archiving

15

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

203

Backup

16

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

Prinergy viii

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

217

Maintenance

17

Performing weekly maintenance tasks...217

Performing monthly maintenance tasks...218

Freeing disk space...218

Compressing the database...220

Disk clean-up tool...221

223

Prinergy updates

18

Updating Prinergy software...223

Deleting the Prinergy 3.x database...224

227

Large systems

19

Prinergy across a WAN...227

Connecting to Administrator on another server...229

231

Glossary

20

ix Contents

Prinergy x

Getting started

1

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

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

Chapter 1—Getting started 2

System overview

2

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

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

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

Software

Acts as the user interface for Prinergy Server software. It is where you control Prinergy Server software and the Prinergy system.

Prinergy Administrator (UADM.exe )

Process PDF files and their contents—for example, trapping JTPs (multiple)

Execute processing that is unrelated to PDF files—for example, job ticket creation, job status and history, imposition, and input file registration

Daemons (multiple)

Launches core processes when the server starts Araxi Service

(Araxi.exe )

These components are installed only on the primary server: Purpose

Software

Stores job information, including file attributes, history information, and pointers to input files—but doesn’t store file content

Oracle® software (Oracle.exe) and database

Backs up the system drive and database to tape or disk. Oracle Backup

Manager

Archives Prinergy jobs (includes archive-related JTPs and Windows RSM)

Prinergy Archiver

Backs up the database to disk Prinergy Backup

Chapter 2—System overview 4

Purpose Software

View PDF files, which are the internal file type of the Prinergy system

Adobe® Reader®

Download and install fonts AppleTalk® Font

Downloader

Calibrate dot gain Harmony®

Edit a Screen Instance File (SIF) to define the screen instances supported by your system and used by Prinergy DotShop

Prinergy DotShop Composer

Access the Prinergy system remotely Symantec™

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.

5 Software components

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.

Chapter 2—System overview 6

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.

7 Servers

Stores jobs? Operating system Server software installed Description/purpose Type of server Yes Windows 2000 Server or Windows 2003 Server

All server software, including the database Coordinates requests from

Workshop and maintains the database Primary server Yes Windows 2000 Server or Windows 2003 Server Administrator One or more JTPs Some daemons Runs some or all JTPs to

distribute processing

For example, an archiving station runs archiving JTPs Secondary servers No Windows 2000 Server or Windows 2003 Server

A secondary server that runs high-resolution rendering software and is connected to an output device Render station Yes Windows is recommended None

Stores jobs. Does not perform processing.

Tertiary servers

No Any server that you

can access None

Stores input files, does not perform processing, and is not called a Prinergy server File servers

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:

Chapter 2—System overview 8

Location Description

Component

In the Jobs folder on the job’s home server Contains the files for a job, including

the system files that Prinergy generates, such as master PDF files and

thumbnails A job folder

named after the job

Either:

● _{UserDefinedFolders folder in the job folder} ● _{Any computer that is visible from the job’s home}

server, such as a file server Customer files that contain the original

information for a printing job, such as PostScript files or imposition plans Input files

An Oracle database on the primary server Information about a job, including the:

● _{Location of all files} ● _{Status of job elements} ● _{History information} Database

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. 9 Distributing the system

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

URL and port Documentation http://server:61235/en/AutoDoc/Index.html RBA Reference http://server:8082/help/ Administrator Help http://server:8083/help/ Connect Workshop Help

http://server:8084/help/ Powerpack Workshop 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.

Chapter 2—System overview 10

Software components

Use

80, unless InSite is using SSL, operates in a DMZ, or requires other specific configurations

http://server/Site/Pages/login.aspx

InSite

80, unless 80 is used, in which case Dashboard uses 51234

http://server:80/Dashboard

Dashboard

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: Default installation folder Situation

C:\Prinergy

New installation with Windows 2003

D:\Prinergy

New installation with Windows 2000

D:\Prinergy 2.0.4

Upgraded version that has not been rehosted

11 Installation folder (%AraxiHome%)

Chapter 2—System overview 12

Licenses

3

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

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:

How It Is Enforced Screens of This Type

Description Type

Not applicable. Creosettes

Included in the base Prinergy license. Included

You cannot selected unlicensed screens in a process template in Workshop. Most screens, including

all screens with names that start with ID Every screen has its own

license. Screen name

licensing

Chapter 3—Licenses 14

How It Is Enforced Screens of This Type

Description Type

You can select unlicensed screens in a process template, but the process fails. Staccato-10,

Staccato-20, and Staccato-25 screens At resolutions of 1440 dpi

and lower, no license is required. At resolutions higher than 1440 dpi, a license is required. Staccato®

screen licensing

If you type a value greater than 1 in the

Highlights box or Shadows box in the MaxTone area in the Calibration and Screening section of an output process

template, and Maxtone screening is not licensed, the process fails.

Maxtone screening Maxtone screening has its

own licensed Maxtone™

screen licensing

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.

Provides advanced profile-based preflighting to identify and correct problems in the input files. Includes a profile

Advanced Preflighting

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. Archives files to store them on tape, purges files to free disk space, and retrieves files from a tape to restore a job.

Archiver

Provides the ability to bi-directionally connect Prinergy with qualified MIS systems using JDF®_{. The production}

Business Link

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 15 Prinergy options

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. Additional Prinergy client licenses are available individually or in 5-packs.

Clients

Enables ICC profile-based proofing and final output.

ColorMatching on Output

Enables output to Brisque® _{CT/LW & TIFF/IT formats.}

CT/LW & TIFF/IT Output

Enables you to create custom reports by connecting the database to third-party reporting software, such as Business Objects™ _{Crystal Reports}®_.

Custom Database Reporting

Increase the number of your Dashboard clients. (The first Dashboard client is free and does not require a license.)

Dashboard

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.

Cuts and collates (de-imposes) the pages from an imposed flat and sends the pages to a printer in reader order.

Digital Blueline Proofing (Signature Booklet)

EPM (Emergency Plate Making) enables you to process jobs and produce plates on a secondary server if a

EPM and Job Replication

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. Additional output engines for low or high resolution.

Output

Chapter 3—Licenses 16

Enables automation of packaging layout creation. It enables Prinergy to automatically take job information

Packaging Layout

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. This Acrobat® plugin provides the ability to

automatically trap PDF pages during a Prinergy refine

PDF Batch Trapping

process (includes advanced features, such as enhanced trap corner geometry settings and keepaway traps for packaging related work).

This Acrobat plugin provides the ability to analyze two PDF files, with the differences being summarized in a

PDF Compare

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.

This Acrobat plugin enables you to edit refined PDF files using Adobe Illustrator®_.

PDF File Editor

This Acrobat plugin assists in correction cycles. It enables you to compare two PDF files, preserve objects

PDF Merge

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.

This Acrobat plugin enables you to add white, bump, and varnish plates to refined PDF files, and gives you

PDF

Platebuilder

an automatic mechanism to create varnish and white separations for appropriate portions of graphics. This Acrobat plugin enables you to trap objects and pages, set trap geometry, and create keepaway traps.

PDF Trap Editor

Dramatically reduces make-ready time by generating digital ink profiles and routing them to the press

PrintLink Ink Key Setting

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.

17 Prinergy options

Automatically gathers information regarding the production of jobs from Kodak Prinergy and InSite. The

Production Reporting

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.

Allows you to create automatic rules for any existing manual event, business process, or daily step in your

Rules-Based Automation

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

Additional refine engines.

Refine

Allows multiple page assignments per page set position. Layered PDF Versioning uses different layers from

Regional Versioning (Layered PDF Versioning)

within a layered PDF to generate different versions within a Prinergy job.

Allows you to run distributed processes on a secondary server in your Prinergy system.

Secondary Server Distribution License

Additional screens available--for example, HyperFlex (screens that allow for smaller dots and/or graphic

Screening

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). Provides linear and non-linear distortion of individual plate separations to compensate for paper stretch in web press operations greater than 37 inches wide.

Web Growth Compensation

Chapter 3—Licenses 18

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

Item

The name of the option—for example, the JTP name

Option column

The number of instances of the option that you are licensed to use. For example, here is where you can see how many Refine JTPs you are entitled to run on your system.

Instances column

The date the option expires—for example, you may be using some options on a trial basis

Expiry Date

column

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.

19 Viewing licensed options

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

Chapter 3—Licenses 20

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.

21 Saving license key information

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.

Chapter 3—Licenses 22

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.

23 Removing a license key

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.

Chapter 3—Licenses 24

JTPs

4

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.

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.

Group Description

JTP Type Icon

Archive Writes whole jobs or individual files onto archiving media.

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

Archive/Retrieve

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

output CEPSConversion

Refine Generates data for color-matching proofs to final output

Color Matcher

Refine and Output Optimizes copydot files for output

Copydot

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

your Prinergy system CopyJob

Output Outputs loose pages to the continuous tone/line work

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

CTLWOutput

Archive Removes selected jobs or files from the job server

Disk Purge

Chapter 4—JTPs 26

Group Description

JTP Type Icon

Generic Perform minor tasks, such as generating thumbnails. The

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

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

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

Generate

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

Heidelberg® _Speedmaster® _{74 DI.}

This JTP is not related to the Digital Print feature of Prinergy. DOP

Output Sends data to the Kodak Xpo™ _{software, which is an interface}

to devices such as the Lotem® _{400 Quantum}® _platesetter Expose

Output Sends data to a Heidelberg Herkules output device

Heidelberg Herkules®

Output Sends data to a Heidelberg Primesetter output device

Heidelberg Primesetter®

Output Sends data to a Heidelberg Quasar output device

Heidelberg Quasar®

Output Sends data to a Heidelberg Signasetter output device

Heidelberg Signasetter

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 the Kodak Page Assigner software.

Import/Export

Refine Converts PostScript language files to PDF, and performs font

management and font handling Normalize

Refine Optimizes PDF files into digital masters that are suitable for

print and checks conditions such as compression and downsampling

Optimize

Output Enables Prinergy to output jobs and files in the PostScript 3

file format PostScript Level 3

Output Sends data to a number of Kodak and Heidelberg output

devices, such as the Kodak Trendsetter® _platesetter Print Console

Output Generates PPF (CIP3) files for digital ink key preset systems

PrintLink

27 Types of JTPs

Group Description

JTP Type Icon

Output Create low-resolutionproofing Devices (256 MB) output that

is suitable for proofing Proofing Device

(256 MB)

Output Create high-resolution (512 MB) output that is suitable for

proofing Proofing Device

(512 MB)

Output Sends data to a Heidelberg SpeedWay® _{output device}

Speedway Engine Manager

Output Sends data to a Heidelberg Topsetter output device

Topsetter® _Engine Manager

Refine Perform trapping in Prinergy

Trap (specific JTPs may vary)

Output Enables output of Prinergy pages in DCS-2, separated

PostScript language, or PDF format VectorOutput

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

Column

Graphical indicator of the type of JTP or JTP pool Icon

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

Name

Which server the JTP is active on

This field is left blank for JTP pool entries, because the JTPs in the pool can reside on multiple servers.

Server

Chapter 4—JTPs 28

Describes Column

Type of JTP or JTP pool Type

Status of the JTP or JTP pool

● _{Starting: It is in the process of being added to the server.} ● _{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. Status

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.

29 Starting or stopping a JTP

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 Chapter 4—JTPs 30

2. For archive, output, and refine JTPs, select a specific JTP in the JTP

Type box:

Select one of these JTPs For this

type

● _{Archive/Retrieve} ● _{Disk Purge} Archive

● _{Bridge - Delta Technology} ● _Copydot ● _CTLWOutput ● _DOP ● _Expose ● _{Heidelberg Herkules} ● _{Heidelberg Primesetter} ● _{Heidelberg Quasar} ● _{Heidelberg Signasetter} ● _{PostScript Level 3} ● _{Print Console} ● _PrintLink ● _{Proofing Device (256 MB)} ● _{Proofing Device (512 MB)} ● _{Speedway Engine Manager} ● _{Topsetter Engine Manager} ● _VectorOutput Output ● _{CEPSConversion} ● _{Color Matcher} ● _Copydot ● _Normalize ● _Optimize ● _Trap Refine

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.

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

Chapter 4—JTPs 32

5. For certain JTPs, next to Features, select the check boxes for specific features:

Select For this type of

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}

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

Import/export

● _{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 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 Copydot ● _{Staccato 20 Series} ● _{Staccato 10 Series} ● _{Staccato 25 Series} ● _{MaxTone Screening} ● _{Seamless Screening} ● _DigiCap ● _{Hyperflex Basic} ● _{Hyperflex Advanced} ● _{Kodak IS Screening} DOP, Expose, Heidelberg devices, Print Console, Proofing devices, and Topsetter 33 Adding JTPs

Select For this type of

JTP

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

Site check box.

PrintLink ● _{VectorOutput:DSC 2} ● _{VectorOutput: Separated PS} ● _{VectorOutput: PDF} VectorOutput

See also:

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.

Chapter 4—JTPs 34

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

35 JTP distribution guidelines

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.

Chapter 4—JTPs 36