The execution logging options are presented like this:
Select the Logging Level depending on the level of detail and type of execution logging required from the following options:
None, Warning, Error, Information or Detail.
If there is a particular mapping issue for which you need to generate debug information for troubleshooting purposes, select the ‘Include Debug Information’ option as well. See section Log Target Values for Debug for details.
Notes on Logging Level
- Including Debug information will write the target values for records to log. This can be useful when troubleshooting complex mappings. More is available in the following section Log Target Values for Debug
- All levels of execution logging (other than NONE) will record errors in the log.
- Logging at the ‘Information’ level is recommended for normal use.
- The log entries displayed in the User Interface during execution will only list entries at or below the level you have set. Note that not all log entries are displayed in the User Interface, the file log generally shows more information.
- Note that the logging configuration defined above is for execution logs only. For project design-time logging, use the Project->Logging menu option.
Log File Options
Select the Log File Option to control the generation of the log files as follows:
| Log File Option | Description |
| New Log File for each Execution | Generates a timestamped (date and time) log file for each execution within the project's execution folder |
| Log to Single File | Logs all migration activity to the same file, either default or named, with the option to append or not. |
| One Week Daily Rolling Log | Generates a date stamped log file per day, with any project log files older than 7 days deleted |
| One Month Daily Rolling Log | Generates a date stamped log file per day, with any project log files older than 1 month deleted |
To save the current settings without executing, use the Save Settings button.
To change the Log File Path, click on the button to the right of the Log File Path field, then select a folder from the browser window. Alternatively, use the Set Defaults button to set the Log File Path to the Default for the current project. This also sets the default logging level (Information).
Defining Reporting Options
For information on the options Write Reports to File and Write reports to Reporting Database, please refer to this related article.
With respect to the reporting level, you can define the type of records that are included in the detailed report as follows:
|
Reporting Level |
Description |
|
Errors and Warnings |
Generates a report just on any errors and warnings found during migration; |
|
Un-migrated Entries and Warnings |
Generates a report on records that weren't migrated and any Warnings that were produced as part of the migration; |
|
All Entries |
Generates a report on all records in the migration; |
If you select the option ‘Produce Migration Report for each Form Mapping’ then the Form Mapping Detailed Migration report is generated with a separate entry for each migrated record. If you de-select this option then only the Summary Report and Summary Form Mapping reports are generated.
Refer to the article on migration reports for details on how to view and filter reports after execution.
Comments
0 comments
Please sign in to leave a comment.