Documentation on Log maintenance of TDM components

Document ID : KB000011808
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

As a System Administrator,  what are the different log files that are used with TDM,  where can I find them and how can i configure them?

Environment:
TDM Common Components: 3.2.2 and laterTDM Portal: 3.6 and later ARD: 2.0 and later
Answer:

For TDM Portal  (based on log4j)

Config file -> C:\Program Files\CA\CA Test Data Manager Portal\conf\logback-tdm.xml

Logs are stored under %PROGRAMDATA%\CA\CA Test Data Manager Portal\logs

Log Appender - *.log.zip files

To turn on debug for details <logger name="com.ca.tdm" level="DEBUG" />

 

 

For ARD the log files are stored under %appdata%/Grid-Tools/logs/AgileDesigner.log

If there is a crash, then a dump file is generated and stored under %appdata%/AgileDesigner/

The logs have a limit of 200MB after which it is deleted (overwritten) and a new files starts.

No the logs for ARD are not configurable outside like log4j. Generally not a lot is logged, but within ARD there is an option under settings where logging can be switched on and off.

  

Datamaker: logs are in %appdata%/Grid-Tools/DM_logs.  Each Datamaker session will have its own log stamped with the a Date and a unique GUID.

TestMatch: logs are in %appdata%/Grid-Tools/Testmatch

TDoD service: logs located under  Grid-Tools\TDoD\TDoD_Service\logs and can be configured using GTWCFHOST.exe.config (log4net).

RemotePublish: logs located under  Grid-Tools\RemotePublish\logs and can be configured using DMBatch.exe.config (log4net)

HPALMService: logs located under  Grid-Tools\GTHPALMService\logs and can be configured using GTHPALMServiceConsole.exe.config

GroupJobProcessor: logs located under  Grid-Tools\GTHPALMService\logs and can be configured using GTHPALMServiceConsole.exe.config

GroupJobProcessor: logs located under Grid-Tools\GTGroupJobProcessor\logs and can be configured using gtgroupjobexecutor.exe.config

  

FDM logs are written to %appdata%\Grid-Tools\Fastdatamasker\logs by default – this can be overridden by setting the path in the options file, you can also set how verbose the log is in the options.

GTSubset itself does not write to a log file, the scripts it generates produce log files when run.

If you run GTSubset from a command line, additional messages are written to the command window.