If you encounter errors or exceptions, you can
use the log files and application logging to research the issues and
find resolutions.
The log file names are qm.log, ccm.log, rm.log, jts.log,
and admin.log.
Log files
If you are
using a Tomcat server that is started with server.startup.bat,
the default xxx.log file location
is Install Dir/server/logs.
If
you are using IBM® WebSphere® Application Server, the default xxx.log file
location is WebSphere Install Dir/profiles/AppSrv01/logs.
The
location of the xxx log file is determined by the log4j.properties file
in the JAZZ_HOME/xxx directory.
The default setting for the xxx.log file
is log4j.appender.logfile.File=logs/xxx.log.
For example, the default setting for the jts.log file
is log4j.appender.file.File=logs/jts.log.
Log feeds
Depending on how the product is
configured, messages are provided in either the log or the console
window. If a problem occurs, you or an administrator might be able
to use the application logging to diagnose the problem. If you cannot
resolve the problem without help from IBM Software Support, a support
representative can use the application logging to find more information
about the problem.
You can configure the log4j logging in the
log4j.properties file.
You can view log messages in the console window, the rolling log files,
or a log feed. You can access a log feed from these locations:
- If you are running a secure connection, access the log feed from
this location: https://host:9443/jazz/service/com.ibm.team.repository.common.internal.IFeedService?category=SystemLog,
where host is your host name.
- If you are not running a secure connection, access the log feed
from this location: http://host:9080/jazz/service/com.ibm.team.repository.common.internal.IFeedService?category=SystemLog
where host is your host name.
- For more information about logging, see Crash
kit Frequently Asked Questions on Jazz.net. To view that page,
a Jazz.net account is required. If you do not have a Jazz.net account,
you can register one for free.