Working with PrizmDoc > Administering PrizmDoc > System Configuration > Configuring the PrizmDoc Server > Legacy Configuration > Configuring Log File Locations |
The PrizmDoc Server are made up of several different processes, each of which create and maintain their own logs. The logs are invaluable for diagnosing issues with PrizmDoc Server if they arise. If you find yourself in this situation, please see the topic How to Package Log Files for Product Support to expedite your support request.
The directory where log files are written can be set by the logging.directory property in the central configuration file.
Example |
Copy Code
|
---|---|
logging.directory: /usr/share/prizm/logs |
The following configuration properties have been deprecated and will be removed in a future release. Alter these properties only if not using the central configuration file. |
If you are using legacy configuration, each logging process has a default log file path that you can change if needed. This section will discuss each process one by one and explain how to configure where log files are written.
This section contains the following information:
The Watchdog uses the following default log file paths:
The Watchdog will only keep up to 7 days of log files. To change where the Watchdog log files are written:
Example |
Copy Code
|
---|---|
"paths": { ... "app_log_dir": [ "C:/some/custom/path" ], ... }, |
The Server and Cloud Entry Points uses the following default log file paths:
The Entry Points will only keep up to 7 days of log files. To change where the Entry Points log files are written:
Example |
Copy Code
|
---|---|
"logging": { "logFilePath": "%ALLUSERSPROFILE%/Accusoft/Prizm/Logs/plb.log", "level": "info", "count": 7, "period": "1d" }, |
The PCCIS service uses the following default log file paths:
The PCCIS service will only keep up to 7 days of log files. To change where the PCCIS service log file are written:
Example |
Copy Code
|
---|---|
<target … fileName="C:/some/custom/path/ImagingServices.log" archiveFileName="C:/some/custom/path/ImagingServices-{#}.log" … /> |
Raster Conversion Service, PDF Conversion Service and AutoRedactionService Log Locations can no longer be updated in those respective Configuration files. When using Central Configuration log locations, they are set via the logging.directory parameter. If you choose to bypass the Central Configuration, these values would be set in the watchdog.config: