When standard logging doesn't provide enough information to determine the root cause for a problem, enabling debug may be necessary.
This will detail the steps necessary to enable, manage and disable the Spectrum OneClick Tomcat web server debug for the Performance Management integration.
Helps to determine possible causes for various issues related to the product integration
All supported Spectrum releases integrated with all supported Performance Management releases
Option A: Disable debug
Option B: Disable debug via service restart.
Disabling debug via Option A disables further logging but won't rotate the logs if they have become large.
To disable the debug and rotate the logs at the same time, restart the restart the tomcat web server service.
Or change the /opt/CA/PerformanceCenter/DM/resources/log4j2.properties file
Uncomment these lines:
#logger.DataSourcePull.name = com.ca.im.portal.dm.productsync.DataSourcePull
#logger.DataSourcePull.level = DEBUG
#logger.DataSourcePush.name = com.ca.im.portal.dm.productsync.DataSourcePush
#logger.DataSourcePush.level = DEBUG
On Portal web page Manage Data Sources select Spectrum and Perform a Full Resynchronization
This will generate logging in the Portal machine /opt/CA/PerformanceCenter/DM/logs/DMService.log file.
Note: To disable Debug back to the original /opt/CA/PerformanceCenter/DM/resources/log4j2.properties file