Connect Logs
Applies to: server-side and client-side Connect processing Concerns: Administrators, Integrators
primedocs Connect writes no log of its own. Connect calls are written to the existing server or client logs, depending on the processing path. This page shows where you can find the relevant entries.
Where are Connect logs located?
| Processing path | Log location | File |
|---|---|---|
| Server-side (via the Connect API) | Server application | serverApp.oolog |
Client-side (.pdcx/.pdck, console, URI call) | primedocs Desktop | Client log (e.g. PrimeDocs.Client.txt) |
Server-side processing
When document generation is triggered server-side via the Connect API, the entries end up in the serverApp.oolog of the responsible server application. You download this file 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:
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 Monitoring). Server-side Connect calls are marked there in the application column with the value Connect.