Activating logging

Activating logging in command line version

New parameter:

--trace[=folderpath]

Example:

./pdfToolbox --trace='/some-logging-folder'  './some-pdftoolbox-profile.kfpx'   './input.pdf'  -o='./output.pdf'

Subfolder structure

By default the logging feature creates a subfolder structure inside the target folder for logging based on values for year, month and day, plus the app_uuid value (which can also be found inside each of the logging files):

 

YYYY
  MM
    DD
      app_uuid
        launch.json
        init.json
        finish.json
Click to copy 
2016
  10
    31
      0a0ceba3-7ca9-421f-a973-8caae2950690
        launch.json
        init.json
        finish.json
Click to copy

Suppressing creation of subfolder structure

New parameter:

--trace_nosubfolders

Example:

./pdfToolbox --trace='/some-logging-folder'  --trace_nosubfolders './some-pdftoolbox-profile.kfpx'   './input.pdf'  -o='./output.pdf'

Activating logging in Server version

In the "pdfToolbox Server: Job" configuration window, add the following to the text field under "Additional CLI parameters":

--trace[=folderpath]

Example:

--trace='/some-logging-folder'

Suppressing creation of subfolder structure in Server version

In the "pdfToolbox Server: Job" configuration window, add the following to the text field under "Additional CLI parameters":

--trace[=folderpath] --trace_nosubfolders

Example:

--trace='/some-logging-folder'  --trace_nosubfolders

Important note: If logging is to be enabled for processing of all files in pdfToolbox Server, this setting must be added to each job configuration.

Activating logging in Desktop version

When "Log Profile Execution" (can be found in the menu in upper right of Profiles/Checks/Fixups window) is activated, then a sub folder "Additional logging" will be created if not already present, and inside that folder the logging files will be added in the same fashion / with the same naming conventions and sub-folder structure as for the CLI and Server version.