Relevant event logs

Use the event logs to analyze events that were recorded by IBM® Content Collector in the Security, System, Application and CTMS_ event logs. After checking the Content Collector dashboard, the event logs are the next place to look for errors.

See Using event logs for details on how to work with event logs in Content Collector and interpreting event logs to understand how an event log error is structured. The relevant event logs for error determination in Content Collector are the following:
  • Application: This is where to look if there is an error in the IBM Content Collector Task Routing Engine service and any of the connectors.
  • CTMS_task_route_name: This task route specific event log records the following type of information: is the connector running, or was anything submitted to the task route for processing. The various log levels that you can set in the IBM Content Collector Configuration Manager, for example, for the IBM Content Collector Task Routing Engine service or the source system and repository connectors has no impact on what is written to the event logs.
  • CTMS_UI: This is the place to look for IBM Content Collector Configuration Manager errors.
  • Text Extraction Connector: This is the place to look for errors if your task route archives documents to IBM FileNet® P8 and uses the IBM Legacy Content Search Engine. This connector does not write to a collector-specific log file like all other Content Collector connectors do. It writes all errors to the event log.