Each PaperCut application server (including the reporting server) must be configured with an external database (see the section called “Overview” in the external database chapter). This database must be accessible for read access from the central server by a nominated URL, user and password.

Central Reports works by running SQL queries on the remote PaperCut databases directly. It is therefore possible as an alternative approach to use other mechanisms to replicate the remote databases to your reporting server and run reports from the local read-only replicas. In this manual, however, we will document only the usual approach of accessing remote databases directly.

All databases must be of the same type. For example, if you use Microsoft SQL Server at one site, this database type must be used at all sites, including the site doing the reporting.

You should ensure the same PaperCut version is installed at each location, including the central reporting location. More specifically, the databases at all sites must use the same database schema (which can change between PaperCut versions).

By default, Central Reports will not generate reports if any remote databases are unavailable or return errors. It is often better to log these events as errors rather than generate potentially incomplete and misleading reports. Central Reports has a Status page which gives you a quick snapshot of the readiness of the system and flags any errors.

If desired, you may instruct central reports to generate reports even if some remote databases are unavailable. To configure, see the section called “Server Configuration”.