Identifying whether metadata is missing

Metadata is defined in some tasks and is required by other tasks further down in the task route. If metadata that is required for a task was not defined, the task will fail.

Error identification

Search the IBM® Content Collector Task Routing Engine service log file to locate the task that failed. With the timestamp logged with the failed task, search the task connector log for information about missing parameters which caused the task to fail. If metadata that was required by the task was missing, the missing metadata is logged using the technical metadata source name.

This metadata source name is logged depending on the log level that you defined for the IBM Content Collector Task Routing Engine service in the IBM Content Collector Configuration Manager under Tools > Task Route Service Configuration.

Ensure that you set the adequate log level to identify this kind of error and run the task route again before you begin searching for error strings. The default log file directory is ContentCollector-install-directory\ctms\Log.
Table 1. IBM Content Collector Task Routing Engine service log file and messages
IBM Content Collector Task Routing Engine service log file Log level Search strings
ICC-install-directory\ctms\Log\ibm.ctms.taskrouteservice* where * is a placeholder for the date and possibly a file number. Warning Search for the following string in the log file messages to find which task failed, filtered by the thread ID:
  • consumer

Action

Table 2. Action after error identification
Result Action
Search string cannot be found. Metadata is missing
  • If the missing metadata is required, check for errors in the task connector log files of the task that is missing the required metadata.
  • If the missing metadata is not required, check if the task route is suited for processing the input documents.
No metadata is missing Did the connector fail?