Enabling Wrapper Trace Logging¶
In order to enable wrapper execution trace logging, the configuration parameter ITPCore.LOGGING_MODE must be set in the appropriate application configuration file. This configuration file is <DENODO_HOME>/conf/vdp/VDBConfiguration.properties for the Wrapper Server and <DENODO_HOME>/conf/itp-admin-tool/ITPAdminConfiguration.properties for the Wrapper Generation Tool. The parameter accepts the following values:
ITPCore.LOGGING_MODE=0
Wrapper execution trace logging disabled. This is the default value.
ITPCore.LOGGING_MODE=1
Wrapper execution trace logging enabled. The traces of all the executions of the same wrapper are logged to the same file.
ITPCore.LOGGING_MODE=2
Wrapper execution trace logging enabled. The execution trace of each execution of each wrapper is logged to a different file.
There is an additional configuration parameter ITPCore.LOGGING_FILTER which allows the user to filter out some specific types of trace events and not log them. This parameter goes in the same configuration file as ITPCore.LOGGING_MODE. Possible values are the following:
ITPCore.LOGGING_FILTER=0
All execution trace events are logged. This is the default value.
ITPCore.LOGGING_FILTER=1
Only events which have associated a Trace action are logged. The log level will be ERROR when the handler is “raise error” or “retry and fail if error persists”, and WARN when the handler is “ignore error”.
ITPCore.LOGGING_FILTER=2
Only events not associated to a Trace action are logged.
Note
When executing wrappers developed with previous versions of ITPilot, the two last values has a different meaning:
ITPCore.LOGGING_FILTER=1
Only events which have associated a custom error (a user defined error) are logged. The log level will be ERROR when the handler is “raise error” or “retry and fail if error persists”, and WARN when the handler is “ignore error” or “retry and ignore the error if it persists”.
ITPCore.LOGGING_FILTER=2
Only events not associated to a custom error (a user defined error) are logged.