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 9.2, “User Client Deployment”
|
jmx/
| |
linux/
|
.desktop templates. |
providers/
| |
cups/
| |
nfc/
| |
server/
|
Section 15.1.1.3, “Internal Admin Password”
Section 4.11.13.4, “JMX Agent”
Section 11.5, “Advanced Configuration”
|
bin/
|
|
custom/
|
Section C.6, “SSL Key Generation”
Section 18.1, “Custom Web App”
|
cups/
| |
i18n/
| |
template/
| |
i18n/
| |
data/
|
Section 15.6, “Encrypted Secrets”
Section J.1.6, “Google Cloud Directory”
|
backups/
| |
conf/
|
Section 4.11.1.4, “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 |
email-outbox/
|
|
internal/
| |
Derby/
| |
letterheads/
| |
safepages/
|
Also see Section 11.5.10, “Alternative File Locations” and Section 11.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