Multiple Print Servers

Many large networks, or even smaller networks with a legacy design, may be composed of more than one print server. Reasons for separating printers across servers/systems include:

One of the servers on the network needs to be nominated as the primary server. This system runs the Application Server software responsible for providing the user interface, storing the data, and managing the application logic. The system nominated for this task is usually a print server (but could be any server). It needs to be a system with spare capacity to run the PaperCut NG application server software. This system should have good performance, have at least 500 Mb of free hard-disk space, and be included in an off-disk backup routine.

Other print servers are known as secondary servers. These servers run the Print Provider component and communicate back to the central server. The following diagram illustrates this setup.

Secondary server reporting back to primary server (application server)

Figure 14.1. Secondary server reporting back to primary server (application server)

When a client prints to a secondary server, the Print Provider intercepts the print job and forwards the information to the central server for processing. Communication is via XML Web Services over HTTP on the PaperCut Application Server's nominated port (normally port 9191). The web services protocol is specifically designed to facilitate easy firewalling, scalability, and will work over a wide range of network speeds.

PaperCut NG Service Oriented Architecture offers many advantages for network administrators including:

PaperCut NG's SOA design allows advanced setups including:

PaperCut NG Architecture - an advanced configuration

Figure 14.2. PaperCut NG Architecture - an advanced configuration