Common logging

Invoice Processing Agility uses a common log structure to record information, warnings, and errors. This helps administrators to troubleshoot issues easily.

Logging in Invoice Processing Agility is available from both Kofax TotalAgility and the Transformation Server. Logging can be done for various activities in Invoice Processing Agility, such as export, validation, or configuration.

Invoice Processing Agility logs the following types of information.

  • Logging level

  • Process ID

  • Thread ID

  • Timestamp

  • Message

Logging in Invoice Processing Agility can be configured with two server variables.

  • Logs are written to the IPALogDir directory. You need to create this directory if it is not configured.

  • The minimum level used is IPALogLevel.

The following log files are created.

  • IPA_CoreWorker.log

  • IPA_TransformationServer.log

    This is generated by the Transformation Server and contains details from the validation phase.

  • IPA_Web.log

  • IPA_Extraction.log

    This is generated by the Transformation Server and contains details from the extraction phase.

Note Since the Transformation Server usually starts multiple extraction process instances and every extraction process instance uses its own log file, the log files for the extraction server have a number as a suffix, such as IPA_Extraction1.log or IPA_Extraction2.log.

The log files for the Transformation Server, that is IPA_TransformationServer.log and Web, that is IPA_Web.log can also have numbers as suffixes if multiple instances are running on a single machine.