Prerequisites for Central Reports
Your organization needs at least two production Application Servers to use Central Reports. You can configure Central Reports on one or both of these Application Servers. You can also configure Central Reports on a separate PaperCut NG/MF installation used solely for the Central Reports feature.
Each PaperCut NG/MF Application Server (including the reporting server) must be configured with an external database (see Deployment on an external database (RDBMS). 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 NG/MF 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. This manual, however, documents 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 NG/MF 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 NG/MF versions).
By default, Central Reports do 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 that gives you a quick snapshot of the readiness of the system and flags any errors.
You can instruct central reports to generate reports even if some remote databases are unavailable. To configure, see Server Configuration.