Choose your language

Choose your login

Contact us

Deployment on an external database (RDBMS)

Available to customers on:

This section describes the process of running PaperCut NG/MF on an external relational database, and describes why you would choose to do this. By default, PaperCut NG/MF uses an internal database product known as Apache Derby. This database engine was donated to Apache by IBM and was previously known as IBM Cloudscape.

The internal PaperCut NG/MF database is stable, scalable, self-maintaining, and provides very good performance. For this reason, most organizations do not need an external database system. However, you might consider running PaperCut NG/MF on an external RDBMS if:

  • Your organization has existing database infrastructure and wants to consolidate all applications on the same database platform.

  • Your organization has an existing database maintenance and backup procedure and wants PaperCut NG/MF to take advantage of this.

  • People want to use 3rd party reporting and analysis tools (like Crystal Reports or Microsoft Access) to view and analyze the PaperCut NG/MF database.

  • Your organization is very large and requires the performance benefits of a dedicated RDBMS. This also allows the database to reside on a separate server to PaperCut NG/MF, which improves the system scalability.

See the PaperCut MF System Requirements and PaperCut NG System Requirements pages (under Database Servers) to see which external databases are supported out-of-the-box. ​​​​​These databases were chosen to cater for the majority of customers.

For more information on supported databases, see the External Database Support Policy .

What’s next?