Tracing messages

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.

The following table describes the types of tracing messages that the i2 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.

Example:

'2002/07/10 15:01:46.812:
 This is version 1.0 of the i2 Adapter'.
 
Level 1 Messages delivered each time the pollForEvents method is executed.
Level 2
  • Messages logged each time a business object is posted to the integration broker from gotApplEvent.
  • Messages that indicate each time a business object request is received.

Level 3 Not applicable
Level 4
  • Application-specific information messages, for example, messages showing the values returned by the functions that parse the business object's application-specific information fields.
  • Messages that identify when the connector enters or exits a function, which helps trace the process flow of the connector.

Level 5
  • Messages that indicate connector initialization, for example, messages showing the value of each configuration property retrieved from the integration broker.
  • Messages that comprise a business object dump. At this trace level, the connector outputs a textual representation of the business object it is processing before it begins processing the object (showing the object the connector receives from the collaboration), and after it is done processing the object (showing the object the connector returns to the collaboration).

Copyright IBM Corp. 1997, 2003