The PaperCut NG / MF solution was designed with distribution in mind. The solution is built using a service-oriented architecture, which allows its components to be installed on different machines with different operating systems. This allows PaperCut NG / MF to be installed in a variety of configurations, adapting to your network design, since no two sites are the same.
The simplest and most common installation is to install PaperCut NG / MF on a website's print server (where the website only has one). For a small school or organization, the implementation need not be more complex than that. It is a single application server, a single print server and suitable for most deployments.
A few more complex implementation examples exist below, to show what is possible. You can extend or merge some of these concepts to suit your network and create the ideal PaperCut NG / MF implementation.
PaperCut NG / MF operates on a layer above your network's print services. For this reason, first design your solution to provide your printing services, then integrate the PaperCut NG / MF application into your network. that is, if you want a site-specific print server to stop large jobs running on network links, do so. You can also use the cluster to provide a long timeout for print services.
PaperCut site server
The PaperCut website server can complete all solution projects in the next section.
The PaperCut website server offers customers the risk of losing peace of mind that access to print resources is not interrupted by unexpected network interruptions. The PaperCut website server implementation ensures that essential PaperCut core server services are supported locally in the event of a disaster. Site servers are easy to install and hide the complexity of database replication from administrators.
Although it was originally designed for use in multi-site solutions, it is not the only use of the site's server. Think of the site server as an application server proxy that can also perform a set of application server tasks with the last known data set during an outage.
Examples of implementation
Scenario A: single site, multiple print servers
It is quite common for websites to have multiple print servers, even if they are clients in one physical location.
IOS printing: implement multimedia printing from iOS devices using a Mac server to complement a Windows print server.
Administrator / Curriculum: Several schools separate the printing in the School Administration section from the general printing of the staff / student.
Pooling - Each node of a pooled resource is installed as a print server.
Each of the print servers in this scenario must be installed and configured to communicate with the application server. For more information, see Configuring secondary print servers and locally connected printers.
PaperCut Site Server could add benefits to this deployment scenario if the application server is deployed in the private cloud. The site server would provide a local level of redundancy in the event of a connection failure to cloud resources. One of the print servers could play this role, in addition to hosting the print provider PaperCut.
Read More - Network Server Deployment
