Configuring the BMC Impact Integration Web Services logs

The IIWS trace log file location and the logging levels are defined in $IIWS_HOME\Tomcat\webapps\imws\WEB-INF\classes\jog4j.properties. After installation, the default log file is set as $IIWS_HOME\Tomcat\logs.

For example on Windows, the default log file could be set to the following:

log4j.appender.F. File=C:/Program Files/BMC Software/Impact Web Services/Tomcat/logs/iiws.log 

You can modify the value to set it to a different file or path. However, you must set the value to a full path.

To generate the debug log file for a package, you can uncomment the desired line by removing the # at the beginning of the line.

This sets the DEBUG level to log4j.logger.com.bmc.ws.common, which prints out the DEBUG information into a log file.

Guidelines for using DEBUG to diagnose issues

Use the following information as a guide when diagnosing issues.

• To diagnose issues in sending events, set the following lines to debug:
  • log4j.logger.com.bmc.sms.imapi
  • log4j.logger.com.bmc.sms.imapi.gw
  • log4j.logger.com.bmc.sms.cellcomm
  • log4j.logger.com.bmc.ws.common
  • log4j.logger.com.bmc.imapi._2010._01
• To diagnose issues in queries, set the following lines to debug:
  • log4j.logger.com.bmc.sms.imapi
  • log4j.logger.com.bmc.sms.imcomm
  • log4j.logger.com.bmc.ws.common
  • log4j.logger.com.bmc.imapi._2010._01
• To diagnose issues in receiving subscription events, set the following lines to debug:
  • log4j.logger.com.bmc.sms.imapi
  • log4j.logger.com.bmc.sms.imcomm
  • log4j.logger.com.bmc.sms.imcomm.cellclient.filter
  • log4j.logger.com.bmc.sms.imcomm.rtr
  • log4j.logger.com.bmc.ws.common
  • log4j.logger.com.bmc.imapi._2010._01