Tracing is an optional debugging feature you can turn on to
closely follow adapter behavior. Trace messages, by default, are
written to STDOUT. See the connector configuration properties for
more on configuring trace messages. For more information on
tracing, including how to enable and set it, see the
Connector Development Guide .
What follows is recommended content for trace messages.
- Level 0
- This level is used for trace messages that identify the adapter
version.
- Level 1
- Use this level for trace messages that provide key information
on each business object processed or record each time a polling
thread detects a new message in an input queue.
- Level 2
- Use this level for trace messages that log each time a business
object is posted to InterChange Server, either from
gotApplEvent() or executeCollaboration().
- Level 3
- Use this level for trace messages that provide information
regarding message-to-business-object and business-object-to-message
conversions or provide information about the delivery of the
message to the output queue.
- Level 4
- Use this level for trace messages that identify when the
adapter enters or exits a function.
- Level 5
- Use this level for trace messages that indicate adapter
initialization, represent statements executed in the application,
indicate whenever a message is taken off of or put onto a queue, or
record business object dumps.
