Tracing is an optional debugging feature you can turn on to closely follow a connector's behavior. Tracing messages are configurable and can be changed dynamically. You set various levels depending on the desired detail. Trace messages, by default, are written to STDOUT (screen). You can also configure tracing to write to a file.
Recommendation: Tracing should be turned off on a production system or set to the lowest possible level to improve performance and decrease file size.
Table 25 describes the types of tracing messages that the Ariba Buyer
connector outputs at each trace level. All the trace messages appear in
the file specified by the connector property TraceFileName. These
messages are in addition to any tracing messages output by the IBM WebSphere
Business Integration Adapter architecture.
Tracing Level | Tracing Messages |
---|---|
Level 0 |
Message that identifies the connector version. No other tracing is done at this level. This message is always displayed; for example,
'2003/03/21 15:01:46.812: This is version 3.0 of the Adapter for Ariba Buyer'. |
Level 1 | Messages delivered each time the pollForEvents method is executed. |
Level 2 |
|
Level 3 | Not applicable. |
Level 4 |
|
Level 5 |
|