SavaPage Open Print Portal can be installed on any modern GNU/Linux system that supports systemd service manager like distributions based on Debian and Red Hat Enterprise Linux (RHEL), and openSUSE. Debian based distributions that use SysV init scripts are also supported.
Throughout this manual GNU/Linux command and file examples are given for Debian based systems. Commands and files might differ for other distributions, but not in function. For example, the Debian apt command has a RHEL yum and openSUSE yast equivalent. It is trusted that system administrators can translate the examples to their own environment. If applicable, functional differences between distributions will be explained.
Installed host package versions are shown in the Admin Web App.
SavaPage is a Java program and must have JDK 11 or higher installed. Check the installation by executing both the java and javac commands: they should echo usage information.
On Debian based systems you can install the JDK package with this command:
sudo apt install default-jdk-headless
SavaPage uses local CUPS printer queues for Proxy Printing. CUPS 1.4 or higher must be installed [4].
On Debian based systems you can install CUPS with these commands:
SavaPage will automatically add any local CUPS printer as proxy printer. So, for proxy printing to work, first add each proxy printer as CUPS printer.
Modern GNU/Linux distributions have everything prepared for using most printers. For USB printers it is often enough to simply plug them in. For network printers you simply start the distribution's printer setup tool out of the system administration menu or out of a system administration application, click on a button for adding a new printer and then follow the screen instructions. If this does not work, usually there is no suitable driver installed on your system. Verify in the OpenPrinting database whether your printer is supposed to work and whether there is a driver or PPD file available. See the OpenPrinting CUPS Quick Start for more details.
An SMTP host must be available for sending email messages. See Section 4.11.4, “Mail”.
SavaPage is packaged with an internal database that offers you the opportunity to evaluate the product on a small scale right away. However, when promoting SavaPage to a production environment with multiple users, we strongly advise you to use PostgreSQL as external database server. See Chapter 21, Using an External Database.
Using the internal database in situations with concurrent use will inevitably lead to locking, deadlock and out-of-memory errors, which can make the system totally unresponsive. See our notes on Database Locking.
SavaPage needs the PDF utilities based on Poppler to function properly.
Poppler is a PDF rendering library based on Xpdf PDF viewer. The command line utilities are used to get information of PDF documents, convert them to other formats, or manipulate them. SavaPage uses pdftocairo to convert PDF pages to images and to Repair PDF documents.
Check if the package is installed by entering the following command:
pdftocairo -v
On Debian based systems you can install the package with this command:
sudo apt install poppler-utils
See Section 13.5.9, “pdf2cairo Image Strategy” if errors are encountered when creating SafePage images.
QPDF is a command-line program that does structural, content-preserving transformations on PDF files. The package is used to decrypt PDF from Web Print and Mail Print when Encrypted PDF for Proxy Printing is allowed. See Section 4.11.13.9, “SafePages”.
Check if the package is installed by entering the following command:
qpdf --version
On Debian based systems you can install the package with this command:
sudo apt install qpdf
wkhtmltopdf is a command line tool to render HTML into PDF. In some cases it may produce better results than the default rendering method. Installation is optional. If installed it is used by default.
Check if the package is installed by entering the following command:
wkhtmltopdf --version
On Debian based systems you can install the package with this command:
sudo apt install wkhtmltopdf
You can disable usage of wkhtmltopdf by setting config property
system.cmd.wkhtmltopdf.enable
value to
N
. See Section 4.11.14, “Config Editor” on how to
change this value.
rsvg-convert is a command-line program that converts SVG images into PNG raster images, PDF, PS, or SVG vector images, or dumps of Cairo XML or recording surfaces. The program is used by SavaPage Draw and needed to handle Standard File Type SVG.
Check if the package is installed by entering the following command:
rsvg-convert --version
On Debian based systems you can install the package with this command:
sudo apt install librsvg2-bin
SavaPage needs the convert command of the ImageMagick software suite to manipulate images.
ImageMagick is a software suite to create, edit, compose and convert bitmap images in a variety of formats (over 100) .
Check by entering the following command:
convert --version
On Debian based systems you can install the package with this command:
sudo apt install imagemagick
Avahi is needed if you want to use IPP Everywhere and AirPrint to print to SavaPage.
Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD [5] protocol suite. Any modern GNU/Linux system has Avahi installed, but to be sure you can check by entering the following command:
avahi-browse --version
On Debian based systems you can install the package with this command:
sudo apt install avahi-daemon avahi-discover libnss-mdns
The SavaPage server process requires a minimum of 2 CPU cores, 2GB of RAM and 1 GB of free disk space.
Depending on the expected print quota you should reserve extra disk-space for each SavaPage user. See Appendix D, Capacity Planning.
On desktop and mobile clients you need an HTML5 compatible browser and support for Internet Printing Protocol (IPP), IP Printing (JetDirect) or AirPrint® .
[4] CUPS 1.4 or higher provides the Job Template attribute “fit-to-page” that is used by SavaPage proxy printing to scale documents to fit the size of selected media. See https://www.cups.org/doc/options.html. Also see Section K.1.1.7, “print-scaling”.