Each of our product services has a separate directory in
the default installation. These product services log files appear
in each of those default installation directories.
The following list defines each type of log file that is under
each service directory.
- autologin.log
- This log includes events that occur during a computer issued login
requests to InfoSphere® MDM Collaboration Server.
- cache.log
- This log includes messages for the object cache manager.
- db.log, db.log.1, db.log.n
- These log files include the executed queries, the time when those
queries were invoked, and how long each query took to complete.
- db_manager.log
- This log includes events that occurred when initializing the database
drivers.
- db_pool
- This log is obsolete and no longer used. InfoSphere MDM Collaboration Server creates
this directory at start up time and output log files to this subdirectory.
However, there is no content inside the log files in this subdirectory.
- dbcontext.log
- This log includes content about the database, such as unexpected
transactional commits and rollbacks. For more information, see Scripting tips.
- default.log
- This log includes the default logger descriptions for InfoSphere MDM Collaboration Server.
For more information, see InfoSphere MDM Collaboration Server log files.
- exception.log
- This log includes all of the exceptions in the appsvr logs directory,
for example, $TOP/logs/appsvr_server_name/exception.log,
for all of the application related issues. It includes all of the
exceptions in the scheduler logs directory, for example, $TOP/logs/scheduler_server_name/exception.log,
for all of the job schedule issues for when a scheduled job fails
on run. It includes all of the exceptions in the workflowengine logs
directory, for example, $TOP/logs/workflowengine_server_name/exception.log,
for all of the workflow related issues. For more information, see Errors in the exception log.
- gds.log
- This log contains UI and scripting errors for the Global Data
Synchronization feature. For more information, see Viewing the Global Data Synchronization log files.
- gdsmsg.log
- This log contains error messages for the Global Data Synchronization
feature.
- javaapi.log
- This log contains events for Java API extensions and implementations.
- mdm_cache.log
- This log contains errors, events, and diagnostic information for
the system cache.
- memory.log
- This log contains information about the memory usage that is collected
after every fixed interval of time that is specified by the memorymonitor_interval parameter.
When the memory monitoring sub-system is enabled and the MEMORY appender
in the $TOP/etc/default/log.xml file is set to
debug mode, a new record is written in the $TOP/logs/*/memory.log file
after each interval defined by the memorymonitor_interval parameter.
For more information, see enable_memorymonitor parameter.
In this example,
the memory monitor is disabled. enable_memorymonitor=false
- mountmgr.log
- This log contains events for the mount manager. For more information,
see Mount manager parameters.
- native_cache.log
- This log contains events for third-party components, such as EHCache,
which also writes messages to a log file. EHCache log file, native_cache.log,
is designated for messages created by this third-party component.
- query.log
- This log contains messages from parsing and processing WQL queries.
- reflect.log
- This log contains messages from running reflection-based script
operations, such as createJavaConstructor or runJavaConstructor.
- request.log
- This log contains http request data for the server in a test or
non-production environment.
- security.log
- This log contains messages when users sign in using single signon.
- servletfilter.log
- This log contains information to help diagnose errors on the user
interface components. This log is important if you have a customized InfoSphere MDM Collaboration Server user
interface.
- soap.log
- This log contains errors and diagnostic information about the
Web services component, which can be used to integrate InfoSphere MDM Collaboration Server with
other applications. Users of stand-alone InfoSphere MDM Collaboration Server deployment
can ignore this log.
- svc.err
- This log contains runtime errors for each JVM. It is the standard
error (STDERR) output.
- svc.out
- This log contains runtime errors for each service creates, and
it should be one of the first log files that you analyze when troubleshooting
a problem. After starting a service, view the svc.out file
for errors or exceptions to ensure that the service started correctly.
For more information, see InfoSphere MDM Collaboration Server log files.
- svc.pid
- This log contains the process ID for the service. For more information,
see pimSupport.sh script.
- trace.log
- This log contains the trace messages when you have turned on tracing.
- workbench.log
- This log contains errors from the Scripting Workbench.
- workflow.log
- This log contains specific events from the workflow engine.