Tracing the execution of events
The Transaction Server can create log messages that provide additional information to use to debug its event processing.
An event handler that is configured to log debug trace messages generates an informational log message every time that it is called to process one of the event types that it is configured to handle. The log message indicates whether the event was successfully processed or whether the criteria in the event stanza were not met. Not all of the event handlers can produce debug information messages, so additional informational messages that indicate whether or not the event handler is running in debug mode are logged.
- EVH00011I - the event handler does not support running in debug mode.
- EVH00012I - the event handler is running in debug mode.
- EVH00013I - the informational log message that is generated by an event handler when it is running in debug mode.
EVH00013I: Risk Profile - File and Presentment States Reached
Presentment state change (id [PRESID[4][0]] state [LOADED] value [2018-05-01 10:09:47.178])
results: Presentment group values did not match: Column value did not match for CONDITION.This
log message indicates that the event stanza named Risk Profile - File and Presentment States Reached
was called to process a PresentmentStateChange event when the state of the batch (ICL) with an ID of 4 was set
to loaded. The event did not result in a message being sent to Risk Management because the
condition column for the transmission was not set to the appropriate value.The following section describes how to configure the additional logging for event handlers.
Enabling or disabling additional logging for an event handler
Additional logging for an event handler is configured in the Scheduler.xml file that is used by the Transaction Server.
<EVENT mode="debug"><EVENT>
<EVENT mode="standard">