Debug logging
As you use LiveCompare, the application creates debug log files in the <LiveCompare user data dir>\public\Logs folder on the LiveCompare server. Working with debug log files requires LiveCompare Administrator permissions. Administrators can configure log file settings, view the log files, monitor their contents, or send them to Tricentis support for problem diagnosis.
Debug log files
LiveCompare names debug log files using the current date or date time. At the start of each day, LiveCompare closes old log files and opens new ones for the current date. If you have switched on server debug logging, LiveCompare creates the following files in the <LiveCompare user data dir>\public\Logs folder on the LiveCompare server.
Server log files
LiveCompare always creates the following log files:
| File | Description |
|---|---|
| ApiToken_<YYYY-MM-DD>.log | Stores details of the API tokens assigned to REST APIs and Web Services. |
| Config_<YYYY-MM-DD>.log | Stores the changes made to LiveCompare’s configuration settings. |
| DSDriver_<YYYY-MM-DD>.log | Stores execution details for LiveCompare’s DSDriver component. |
| Dui_<YYYY-MM-DD>.log | Stores information recorded for LiveCompare’s developer user interface. |
| Apps\Log_Apps_<YYYYMMDD>.txt | Stores the XML input and output to and from the apps user interface. |
| Log_OghmaServerExchange_YYYYMMDD.txt | Stores information recorded for the execution of workflows registered as Web Services. |
| Pii_<YYYY-MM-DD>.log | Stores changes to personally identifiable information. |
| ServerAux_<YYYY-MM-DD>.log | Stores the XML input and output from the auxiliary server. |
| ServerMain_<YYYY-MM-DD>.log | Stores the XML input and output from the main server. |
| Table_<YYYY-MM-DD>.log | Stores information for tables to ignore. |
| wipsrv_<YYYY-MM-DD>.log | Stores execution details for LiveCompare’s Wipsrv component. |
| <WGI program>\<WGI program>_YYYYMMDD_HHMMSSmmm.txt | These log files store information recorded by LiveCompare’s Workflow Gateway Interface (WGI) programs. LiveCompare creates these log files if an Administrator sets the WgiLogFiles field to X in the Configuration - Logging screen. |
Workspace log files
LiveCompare stores log files for each workspace in a folder named <LiveCompare user data dir>\public\Logs\<workspace name> on the LiveCompare server. Each <workspace name> folder contains log files named <workflow name>_YYYY-MM-DD.log.
Test Repository connection test log files
LiveCompare creates the following files in the <LiveCompare user data dir>\public\Logs folder for each of the following Test Repository connection tests:
| Test Repository | Log file |
|---|---|
| ALM | qccontst\qccontst_<YYYY-MM-DD>.log |
| Azure DevOps | adotestconnection_<YYMMDD>_<HHMMSSmmm>.txt |
| Certify | certifytestconnection_<YYMMDD>_<HHMMSSmmm>.txt |
| qTest | qttestconnection_<YYMMDD>_<HHMMSSmmm>.txt |
| SAP Solution Manager | ssmtestconnection_<YYMMDD>_<HHMMSSmmm>.txt |
| Tosca Cloud | tcdcontst_<YYMMDD>_<HHMMSSmmm>.txt |
| Tosca Local | tccontst_<YYMMDD>_<HHMMSSmmm>.txt |
| Tosca REST | tccontst_<YYMMDD>_<HHMMSSmmm>.txt |
Workflow Gateway Interface log files
Workflow Gateway Interface (WGI) programs allow LiveCompare to integrate with Tosca, qTest, and other Test Repositories. If an Administrator sets the WGILogFiles field to X in the Configuration - Logging screen, LiveCompare’s WGI programs create their own log files in addition to the workflow run log.
Set the server log level
The server log level determines the amount of detail that LiveCompare stores in log files. An Administrator can define the level in the ServerLogLevel field in the Configuration - Logging screen. The ServerLogLevel field may have the following values, listed from lowest to highest priority:
| ServerLogLevel | Description |
|---|---|
| trace | LiveCompare logs detailed trace information (where available). |
| debug | LiveCompare logs detailed debug details. |
| info | LiveCompare logs information details. |
| warning | LiveCompare logs warning details. |
| error | LiveCompare logs error details. |
| critical |
LiveCompare logs critical messages. |
| off | LiveCompare logs no messages. |
Each server log level includes the server log levels with higher priority (with the exception of off). For example, error includes both error and critical. If the ServerLogLevel field is blank, LiveCompare uses debug as the default value. This includes the debug, info, warning, error, and critical server log levels.
Rfc and cpic trace logging
LiveCompare supports rfc and cpic trace logging for operations that use an RFC Destination. To enable rfc and cpic trace logging, carry out the following steps on your LiveCompare server machine:
-
Stop the Tricentis LiveCompare Application Server service.
-
Add the following DWORD entries to the HKEY_LOCAL_MACHINE\Software\Tricentis\LiveCompare\2025.2\Settings registry folder.
-
RfcTraceLevel = 4
-
CpicTraceLevel = 3
-
Start the Tricentis LiveCompare Application Server service.
LiveCompare names the cpic and rfc log files as follows:
-
cpic_<cpic identifier>.trc
-
rfc<cpic identifier>_<rfc identifier>.trc
Switch off debug logging
To switch off debug logging, set the ServerLogLevel field to off in the Configuration - Logging screen. If you change the value of this field, you need to restart the Tricentis LiveCompare Application Server service on the LiveCompare server for the change to take effect.
Browse log files
To browse log files, select Browse Logs in the Configuration - Logging screen. LiveCompare displays the Logs screen. You can send individual log files to Tricentis support for problem diagnosis or troubleshooting.
Export log files
To export log files to a time-stamped ZIP file, select Export Logs in the Configuration - Logging screen. Use the Download the file link in the Export screen to download the ZIP file to your own machine. You can send log files to Tricentis support for problem diagnosis or troubleshooting.
Purge log files
To delete the log files on the LiveCompare server, select Purge Logs in the Configuration - Logging screen.
You can purge log files older than the specified number of days by setting a value in the Logging section’s DaysToKeepLogs field. The default value is 7. A scheduled task named Tricentis LiveCompare Purge Reports runs each night on the LiveCompare server to purge log files based on their last modification date.
-
If you set the DaysToKeepLogs field to 0, LiveCompare won't purge log files automatically.
-
If you set the DaysToKeepLogs field to 1, LiveCompare won't purge log files generated on the previous day.
Purge temporary files
You can purge temporary files generated by LiveCompare by setting the following DWORD registry entry on the LiveCompare server:
HKEY_LOCAL_MACHINE\Software\Tricentis\LiveCompare\2025.2\Settings\DaysToKeepTemps
A scheduled task named Tricentis LiveCompare Purge Reports runs each night on the LiveCompare server to purge temporary files based on their last modification date.
-
If you set the DaysToKeepTemps DWORD to 0, or if the registry entry doesn't exist, LiveCompare won't purge temporary files automatically.
-
If you set the DaysToKeepTemps DWORD to 1, LiveCompare won't purge temporary files generated on the previous day.
Client-side logging
If client-side logging is enabled, LiveCompare displays log information in your browser’s Developer Tools console window. To enable client-side logging for all users, set the following DWORD registry entry on your LiveCompare server machine:
HKEY_LOCAL_MACHINE\Software\Tricentis\LiveCompare\2025.2\Settings\ClientLogLevel
You can set ClientLogLevel to any of the following values:
| ClientLogLevel | Description |
|---|---|
| 0 | Logs a full stack trace. |
| 1 | Logs debug messages. |
| 2 | Logs information messages. |
| 3 | Logs warning messages. |
| 4 | Logs error messages. |
After setting or changing the value, select Ctrl+F5 in your LiveCompare browser window to perform a full refresh.
We recommend that you don't enable client-side logging unless Tricentis support asks you to.
Detailed SAP logging
The following String entries in the HKEY_LOCAL_MACHINE\Software\Tricentis\LiveCompare\2025.2\Settings registry folder allow for detailed logging of SAP hexadecimal values returned to LiveCompare:
-
Tier2BasicDebugLogAttrTab = X
-
Tier2BasicDebugLogGetValue = X
You shouldn't normally set these values unless Tricentis support asks you to.