Connect Logs
Applies to: server-side and client-side Connect processing Concerns: Administrators, Integrators
Connect calls are logged by the component that processes them. Depending on the processing path, this is a server application or primedocs Desktop. primedocs Desktop can additionally record the Connect calls it receives in a separate Connect log. The overview of all logs is in Logging.
Where are Connect logs located?
| Processing path | Log location | File |
|---|---|---|
| Server-side via the Connect API | Server application WebApi | serverApp.oolog |
Server-side via the Connect service (/api/v1/Connect) | Server application Connect | serverApp.oolog |
Client-side (.pdcx/.pdck, console, URI call) | primedocs Desktop | PrimeDocs.Client.txt |
| Client-side, Connect log (optional) | primedocs Desktop, %TEMP%\primedocsConnectLogger | one file per call |
Server-side processing
When document generation is triggered server-side, the entries end up in the serverApp.oolog of the processing server application. This file is downloaded like all server logs via the Admin Dashboard:
Client-side processing
When Connect is processed via primedocs Desktop (double-clicking a .pdcx/.pdck file, console or URI call), the entries are written to the client log:
To trace the call that was actually received, the Connect log can additionally be switched on under primedocs › Options › primedocs Connect with Enable logging. primedocs Desktop then saves every received Connect XML as a separate file. The recording ends automatically 24 hours after activation for data protection reasons, see Connect log.
What is logged?
- The receipt of a Connect call.
- At a verbose log level (Debug/Trace), additionally the transmitted Connect XML (useful for tracing the call that was actually received).
- Validation errors (e.g. when no valid Connect action is recognised).
- Errors during document generation.
Connect entries in the database
If the attribute databaseLoggingEnabled="true" is set in the primedocs.config, warnings and errors of the server applications are additionally written to the database and can be viewed in the Logging tab of the DataSourceAdminApp (see Logging to the database). The Application column shows the processing application: WebApi for calls via the Connect API, Connect for calls via the Connect service.