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

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 other job management functions.
• 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.
• Prinergy Primary and Secondary servers support a maximum of 56 Job Ticket Processors of any combination, per server.

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 eight logical CPUs

For a premium server that is configured with eight logical CPUs (that is, two quad-core CPUs, such as the PE R710 or the PE T620), you can 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 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 Normalize JTPs
• 2 Optimize JTPs
• 2 Color Matcher JTPs
• 1 Trap JTP
• 1 Import/Export JTP
• 3 Proof JTPs
• 2 Generate JTPs
• Perhaps 1 or 2 extra Refine JTPs as required.