The majority of SavaPage configuration is conducted in the Administrator Web App. Some additional
configuration options are available in the
/opt/savapage/server/server.properties configuration
file. This file contains server configuration including the server's TCP ports and
SSL properties and Alternative File Locations.
| Key | Description |
|---|---|
|
|
Server http port. Default:
|
|
|
Server https port. Default:
|
|
|
Redirect HTML of non-SSL port to SSL:
|
|
|
The RAW Print Server port. Default:
|
Table 10.2. Server Properties for Alternative TCP/IP Settings
Since SavaPage is run by user
savapage, you can't use ports below
1024, because these ports can only be bound to by the superuser (root).
If you want SavaPage Web Apps to be accessible through port 80 and
443 at all costs, you can use Apache or NGINX server to forward (or "reverse-proxy") requests to
SavaPage.
To separate created files from installation files you can set alternative
locations for temporary files, SafePages and public Letterheads in the
/opt/savapage/server/server.properties
configuration file.
All alternative file locations must reside on the same disk partition[23].
| Key | Description |
|---|---|
| Location of the application's temporary files. It is created when the application starts and removed when stopped. Default:
|
| Location where the user's SafePages are stored. Default:
|
| Location where the public Letterheads are stored. Default:
|
Table 10.3. Server Properties for Alternative File Locations
| Key | Description |
|---|---|
|
|
Enable database cleanup at server start-up. See Section 4.10.13, “Backups”. Values: |
|
|
See Section 17.1.1.4, “Custom i18n”. Values: |
Table 10.4. Server Properties: Miscellaneous Settings
[23] This constraint is needed because files are initially created in the temporary location and atomically moved to their destination. Atomic moves do not work cross-partition.