10.11 Input Agent and Input File Issues

The following issues involve input agents or input files.

10.11.1 Input Agent Will Not Detect and Process Input Files

If the input agent will not pick up input files, try the following steps to determine a solution.

  1. Check the settings of the following Oracle I/PM MBeans:

    • AgentUser: This must be set to a valid user in the security store for the agents to operate. Content Server and I/PM must be restarted if the AgentUser changes. Note that if multiple I/PM systems connect to one Content Server repository, the same AgentUser should be configured for each I/PM system.

    • CheckInterval: Make sure this is set to a reasonable amount of time for your environment (for example, maybe 1 minute for test systems or 30 minutes for production systems that do not need to get data right away) and ensure that enough time has expired for at least one polling interval to have occurred.

    • InputDirectories: Examine the list of directories and ensure that they are the correct directories where the input files are stored.

  2. Ensure that the input file has Read/Write permissions for WebLogic Server.

  3. Check the permissions on the input directory paths and make sure they are accessible to the user that is running the WLS managed server.

  4. Look at the input object in the user interface and make sure the input that is supposed to be processing is marked online and that the input file mask matches the files that are in the directory.

  5. If the input agent is still not running then examine the log files to see if an error was encountered that is preventing the agent from functioning.

10.11.2 Auto-detect Not Determining Character Set

Auto-detect does not work if the provided sample file is not large enough to get an accurate determination of the character set. If the sample file is too small, disable Auto-detect input file character set and manually select the character set.

10.11.3 Input File Entries Have Errors

For the steps below, refer to the following directory structure:

   - Errors
   – Failed
      — YYYY-MM-DD
   – Processed
      — YYYY-MM-DD
   – Samples 
   – Stage

If some or all of the entries in the input file have errors, try the following steps to determine a solution.

  1. Look at the Errors directory in which the input file was placed and see if an error file was created. If an error file exists, then open it and examine the last column of the file to determine the specific error.

  2. Examine the input file and verify that the path to the image file is accessible to the user that is running the Oracle I/PM managed server and that the user has permissions to the path and image files.

  3. Copy one of the failing input files to the samples directory and load it into the input definition editor UI. Verify that the mappings are correct and that one of the columns has not shifted.

  4. Finally, look at the Oracle I/PM log file and examine the errors that are listed for the individual lines to determine the exact cause of the problems.

Once you have determined the cause of the error and are able to correct it, copy the corrected input file back into the input directory. For additional information, see "Checking Results and Error Files".

10.11.4 Dates and Times Shifting on Content Ingested Using Input Agent

Dates and times specified in the input file are subject to current Daylight Savings Time rules, and not the DST rules in effect for the specified date. This can cause the timestamp of the document to shift forward or back up to two hours. If the timestamp shifts forward or back across midnight, the date used for the document input may also shift.