The table below summarizes the SavaPage file locations.
When overriding defaults, make sure the location for SavaPage temporary files resides on the same disk partition as the locations used to store data on runtime. See:
Path | Description |
---|---|
/opt/savapage/
|
Install directory. |
client/
|
Client applications. |
app/
| |
config/
|
Section 11.2, “User Client Deployment”
|
jmx/
| |
linux/
|
.desktop templates. |
providers/
| |
cups/
| |
nfc/
| |
server/
|
Section 17.1.1.3, “Internal Admin Password”
Section 4.11.13.4, “JMX Agent”
Section 13.5, “Advanced Configuration”
|
bin/
|
|
custom/
|
Section C.6, “SSL Key Generation”
Section 20.1, “Custom Web App”
|
cups/
| |
i18n/
| |
template/
| |
i18n/
| |
data/
|
Section 17.6, “Encrypted Secrets”
Section J.1.6, “Google Cloud Directory”
|
.tmp/
|
Default location for temporary files, created when the
application starts and removed when stopped. Location can be
changed with the |
backups/
| |
conf/
|
Section 4.11.1.5, “Internal Groups”
|
docs/
|
Accessible via URL: Appendix E, URL Cheat Sheet |
doc-archive/ out/print/ [CCYY]/ [MM]/ [DD]/ [HH]/ [UUID]
|
Printed PDF and Job Options (in JSON format) are stored in a unique identifying file path of year, month, day, hour and UUID of the print job. |
doc-journal/ out/print/ [CCYY]/ [MM]/ [DD]/ [HH]/ [UUID]
|
Analogous to |
doc-journal/ in/print/ [CCYY]/ [MM]/ [DD]/ [HH]/ [UUID]
|
Analogous to |
email-outbox/
|
Outgoing email queue. |
internal/
| |
Derby/
| |
letterheads/
| |
safepages/
|
Also see Section 13.5.10, “Alternative File Locations” and Section 13.5.7, “User Home Clean”. |
print-jobtickets/
| |
examples/
| |
papercut/
| |
ext/
|
|
lib/
|
Extension JAR files. |
logs/
|
Extension log files. |
lib/
|
Main WAR and JAR files.
|
logs/
|
Main log files. |
Table F.1. SavaPage File Locations