Log files

The TADDM server creates log files about its operation and stores these log files in the $COLLATION_HOME/log directory. Log files can help you in troubleshooting problems with discovery or with the function of the TADDM server.

Table 1 lists the general log files in TADDM. Table 2 lists additional log files that are present in a synchronization server deployment, and Table 3 lists additional log files that are present in a streaming server deployment.

If a log file is in the $COLLATION_HOME/log directory itself, only the file name is listed. If a log file is in a lower-level directory in the $COLLATION_HOME/log path, the additional path information is shown with the file name.

TADDM.log is the product log file that contains only informational messages for users. The other log files contain trace information that might be useful to both users and IBM® Software Support. The following log files are typically the most useful:
  • error.log
  • local-anchor*.log
  • sensors/runid/sensorName-IP.log, if you use split logging
  • services/DiscoverManager.log
  • services/TopologyManager.log
  • TADDM.log and TADDM-component.log
  • tomcat.log (TADDM 7.3.0)
  • wlp.log (TADDM 7.3.0.1, and later)
Table 1. General log files
Log file Information contained in log file
agents/*.log Information from the topology builder agents that is split into different log files that reference individual agents
appexit.log Information about stopping the TADDM server on computers that are running Windows operating system
dist/log/bizapps/<pattern>/<starttime>.log Information about the business applications processing with the use of composition engine, when split logging is enabled. The <pattern> folder is created for each grouping pattern and contains <starttime>.log files, which represent each processing of the grouping pattern.
bulkload.log Information about the bulk load program
change-events.log Information about change events that are sent to IBM Tivoli® Netcool/OMNIbus
changeevents_out.log Information about change events that are sent to IBM Tivoli Netcool/OMNIbus
control.log Information about the starting and stopping of the TADDM server
discover.log Information from the Discover service
discover-admin.log Information from the DiscoverAdmin service
error.log Error messages from TADDM services
events-core.log Information from the EventsCore service
local-anchor*.log Information from Java EE application server sensors, such as WebSphere® and WebLogic
Fix Pack 2 logger-internal.log Potential information from the preparation of the log messages.
login.log Information about user logins (for audit purposes)
l2.log Information from the topology builder process
migration.log Information that is related to upgrading TADDM
mighist/changedGuids-time-stamp.xml
migration/TADDM-version/time-stamp-DbConfiguration.log
migration/TADDM-version/time-stamp-DbMessages.log
migration/TADDM-version/time-stamp-PrimarySchema.log
migration/TADDM-version/time-stamp-SecondarySchema.log
migration/TADDM-version/time-stamp-GuidByClass.log
migration/TADDM-version/time-stamp-GuidByID.log
migration/TADDM-version/time-stamp-Templates.log
migration/TADDM-version/time-stamp-SensorConfiguration.log
proxy.log Information from the Proxy service
plugins/plugins-sensors.log Information from the pluggable sensor loader
sensors/runid/sensorName-IP.log If you use split logging, information about sensor activity.

The runid includes the date and time of the discovery. The sensorName-IP (the log file name) includes the sensor name and the IP address of the target system. The following example is a log file on the TADDM server: $COLLATION_HOME/log/sensors/20070621131259/SessionSensor-10.199.21.104.log.
services/ApiServer.log Information about TADDM APIs
services/AuthorizationManager.log Information about logins to TADDM
services/ChangeManager.log Information about the processing of change events after discovery completes
services/ClientProxy.log Information about the GUI
services/DiscoverManager.log Information about sensor activity
services/DiscoverObserver.log Information about the movement of completed work items from the discover manager to the topology manager
services/PatternsSchedulingService.log Information about the business applications processing with the use of composition engine
services/ProactiveRequests.log Information about incoming proactive requests and the results of these requests (for audit purposes). The log also contains information about the number of proactive requests that are pending in the work queue.
services/ProfileManager.log Information about storing and retrieving discovery profiles
services/ProcessFlowManager.log Information about the event processing engine for discovery
services/ReconciliationMerge.log Information about merging that has occurred between two or more configuration items that are stored in the database
services/ReconciliationPlugIns.log Information about the activity of reconciliation plug-ins
services/ReportsServer.log Information about the processing of reports
services/SecurityManager.log Information about the security activities of the TADDM services
services/Semaphore.log Information about the semaphore service in TADDM
services/Template.log Information about the custom templates that are used in TADDM
services/TopologyBuilder.log Information from topology builder agents
services/TopologyManager.log Information about the interface between the data store and all other components
services/ViewManager.log Information about the building of the topology graphs and navigation trees for configuration items
TADDM.log The TADDM component log files contain the following information:
  • Information about starting and stopping the following processes:
    • bulkload
    • discovery
    • sensor
    • sensor result storage
    • topology builder
    • topology builder agent
    • change propagation
    • view build
    • synchronization server
  • Messages about the following items:
    • Logon and logoff from the user interface (UI)
    • Connections to an API
    • Closing of the API session
    • Timeout errors
TADDM-Discovery.log
TADDM-DiscoveryAdmin.log
TADDM-EventsCore.log
TADDM-Proxy.log
TADDM-Topology.log
tomcat/cdm-rest.log (TADDM 7.3.0) Information about UI services
tomcat/cdm-webapp.log (TADDM 7.3.0) Information about UI services
tomcat.log (TADDM 7.3.0) Information about application server activity
topology.log Information from the Topology service
trace.log This log is generated by the WebSphere client that is used in the IBM WebSphere sensor.
win-service.log Information about the Windows operating system. This log applies only to computers that are running the Windows operating system.
wlp/cdm-rest.log (TADDM 7.3.0.1, and later) Information about UI services
wlp/cdm-webapp.log (TADDM 7.3.0.1, and later) Information about UI services
wlp.log (TADDM 7.3.0.1, and later) Information about application server activity
Table 2. Additional log files in a synchronization server deployment
Log file Information contained in log file
ecmdb-core.log Information from the initialization of the core service in a synchronization server deployment
services/Synchronizer.log Information from the synchronization process in a synchronization server deployment
sync/computer-FQDN.log computer-FQDN represents the fully qualified domain name of the computer where the Data Management Portal is being used.

This log contains the messages that are sent to the View Sync Details window in the Data Management Portal. To help you evaluate the status of the synchronization, it contains only the most important events that occur during the synchronization process. $COLLATION_HOME/log/services/Synchronizer.log contains much more detail about the synchronization process.
Table 3. Additional log files in a streaming server deployment
Log file Information contained in log file
DiscoveryService.log Information about the discovery server activities
StorageService.log Information about the storage server activities