Running traces on the Service Manager web client

Specify trace parameters in the log.properties file. This allows flexible configuration according to analysis requirements. In order to activate the modifications, the web application server must be restarted.

Example: A standard web tier trace configuration referred to as “CWC debug trace”

log4j.rootLogger=debug,R
#log for trace soap message, don't modify it.
log4j.logger.TraceSoap=DEBUG, R
log4j.additivity.TraceSoap=true
#uncomment next line to output to console.
#log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
# Pattern to output the caller's file name and line number.
log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=sm_CWC_debug.log
log4j.appender.R.MaxFileSize=500000KB
# Keep one backup file
log4j.appender.R.MaxBackupIndex=9
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=[%d{yyyy-MM-dd HH:mm:ss}] %p %t %c - %m%n
log4j.logger.com.peregrine.eclipse.web=DEBUG
log4j.logger.com.hp.ov.cwc=DEBUG
log4j.logger.TraceSoap=DEBUG

There is rarely the need for a web tier trace. However, in these cases, typically it is required to also trace browser communications using third-party tools (such as Fiddler and Wireshark) and the Service Manager server.