Hi all, we often ask anyone facing an issue to run their tests again with debugging on in order to help us investigate the issue further, so I wrote a knowledge doc on how to do just that.
You will be able to find this knowledge base article, along with others at http://www.ca.com/us/support/ca-support-online/support-by-product/ca-test-data-manager.aspx
This document will outline how to enable debugging for Test Data on Demand (TDoD).
If you are experiencing any issues while using Test Data on Demand (TDoD) and either want to get more information on why you are experiencing the issue or need to send log files to CA Support, enabling debugging is a good first step. This form of debugging requires you to alter a configuration file and cannot be done through the user interface.
Test Data on Demand (TDoD)
TDoD is installed as part of the CA Test Data Manager (TDM) product.
Release versions of TDM 3.1 and above.
Pre-requisites: Please exit out of the TDoD Configuration Editor before editing any configuration files.
1. First you will need to go to your GTWCFHOST.exe.config file.
- The default location for that is located at C:\Grid-Tools\TDoD\TDoD_Service\GTWCFHOST.exe.config
2. Open the file by right clicking on it and choosing ‘Edit with Notepad ++’, or another similar program.
- If you double click on the file to open it, it will usually open in Visual Studios or another program that will not work for editing.
- If you do not have Notepad ++ installed, and would like to, you can Download Notepad ++ by clicking the link.
3. Once inside the file, search for the line <filter type="log4net.Filter.DenyAllFilter" />
- You can press 'Ctrl + F' on your keyboard, and paste that line into the 'Find what' box that appears to search for this.
- You can also click 'Search' at the top of the toolbar, choose 'Find' from the drop down, and paste that line into the 'Find what' box that appears.
- This line will be found in two places and each will need to be edited.
4. Comment out this line by putting <!-- in front of it and --> after it.
- The line should now look like <!-- <filter type="log4net.Filter.DenyAllFilter"/> -->
5. Repeat steps 3 and 4 to comment out the second occurrence of this line.
- Only this one line should be commented out. Make sure not to comment out the entire section.
6. Save your changes by clicking on ‘File’ at the top of the page, and choosing ‘Save’ from the drop down list.
7. Re-open the TDoD Configuration Editor by double clicking on the TDoDConfigEditor.exe.
- The default location for this is at C:\Grid-Tools\TDoD\TDoD_ConfigEditor\TDoDConfigEditor.exe
8. Under the ‘Configure Portal’ tab, and within the ‘Settings’ tab, make sure that your Service URL and/or ALM Service URL are set to the correct machine names.
9. Click the ‘Save’ button.
10. Click the ‘Verify’ button and take note of any error messages.
11. Under the ‘Configuration Service’ tab, and within the ‘Connection String’ tab, make sure that your Database Type, Data Source, User ID, and Password are correct.
12. Click on the ‘Save’ button.
13. Click on the ‘Verify’ button and take note of any error messages.
14. Click the ‘Stop Service’ button.
15. Click the ‘Start Service’ button and take note of any error messages.
16. After the service has been started, or failed to start, look in your tdod.log file.
- The default location for this is at C:\Grid-Tools\TDoD\TDoD_Service\logs\tdod.log
If you are seeing logs in this tdod.log file, then you have successfully enabled debugging for the TDoD Service.
If you experience any further issues, please open a support case.