Logging

Logging can be done through files or database logs.

File Logging

You can set up and generate file-based logging in these ways.

  • Specify logging in the transformation properties in a job.

    Open the transformation properties and click the Logging Setting tab.

    Consider to specify these check boxes and fields:

    Specify logfile?
    Select this check box to create a log file.
    Append logfile?
    Select this check box to append the log file to the job.
    Name of the logfile
    Specify a logical name.
    Create a parent folder
    Select this check box to specify a location to save the log file.
    Extension of logfile
    The extension of the file
    Include date in logfile
    Yo can include the date in the log name.
    Include time in logfile
    Yo can include thetime in the log name.
    Loglevel
    Specify the level. There are seven levels.
  • Set up logging in the Windows batch script that runs the job.

    You can find an example of a script with log file in this folder: x:\Infor\IONETL\Infor_ION_ETL_%version%/deem_setup/jobs

    An example:

    @echo off
    setlocal
    set d=%date%
    set t=%time%
    if "%t:~0,1%"==" " set t=0%t:~1,4%
    set cdate=%d:~6,4%%d:~3,2%%d:~0,2%
    set logfile=d:\deem\Jobs\log\job_finance.log
    echo Start: %date% %time% >> %logfile%
    
    
    D:
    cd %DI_DESIGNER%
    call %DI_DESIGNER%\Kitchen.bat /rep:prd /job:job_finance /dir:/mi_finance /user:admin /pass:admin /level:Basic %logfile%
    

    You can enhance the scripts further when required.

Database logging

Database logging is available at job and transformation level. When logging is active, you can see the logging within the opened job or transformation.

  • Job level database logging is set up in the jobs properties in the Log tab. You can configure in a logging database these types of job logs: .
    • Job log table

      This log captures log history of every time the job is run including this information:

      • Status - start, end, stop, error, running, paused.
      • Start Date - the start-date of the date range that is calculated each time you run the job. The end date of the previous run.
      • End Date - the end-date of the date range that is calculated each time you run the job. It typically is sysdate at start-time of the transformation.
      • Log Date - The sysdate of the start-time of the job.
      • Log File - Job level logs for the complete job, up to field size limit.
    • Job entry log table

      This log captures the history for each step setup in the job and the run result. Success – 1, Failed – 0.

    • Job channel log table

      This log links the job information with the transformation channel steps for consistency.

  • Transformation level database logging is set up in the transformation properties in the Logging tab. You can configure several transformation logs in a logging database of these types:
    • Transformation

      Transformation logs works much like the Job log table described earlier. This log captures run history of every time the transformation has run including this information:

      • Status - start, end, stop, error, running, paused.
      • Start Date - the start-date of the date range that is calculated each time you run the transformation. The end date of the previous run..
      • End Date - the end-date of the date range that is calculated each time you run the job. It typically is sysdate at start-time of the transformation..
      • Log Date - The sysdate of the start-time of the job.
      • Log File - Job level logs for the complete job.
    • Step

      Logs captures each transformation steps Inputs, Outputs, Read, Writes, and Updates information

    • Performance

      Logs captures step performance monitoring. The step performance check box on the Monitoring tab of the transformation properties configuration must be checked.

    • Log channel

      Logs captures the links between the job run and transformation run if the transformation was run through a job. If the transformation was run independently through the application, there is no link found in the Job Log Channel logging table.