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).
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 Retek
connector outputs at each trace level. These messages are in addition
to any tracing messages output by the WebSphere business integration
system's architecture, such as the Java connector execution wrapper and
the IBM WebSphere MQ message interface.
Tracing level
| Tracing message usage
|
Level 0
|
Message that identifies the connector version.
Example:
'2002/07/10 15:01:46.812:
This is version 1.0 of the Retek adapter'
This message is always displayed.
|
Level 1
|
- Status messages
- Messages that provide identifying (key) information for each business
object processed.
- 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
|
- Messages that provide information about business object processing, such
as event retrieval (GETNXT), payload-to-business object transformation (XML
data handler usage), and business object processing (CONSUME).
|
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.
- pollForEvents statistics: information on events retrieved by each
polling thread for each poll cycle (message family, number of events), and
overall polling cycle statistics: pollQuantity, actual number of events
received, duration of poll cycle, and others.
|
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 textual representation of the business object
before the connector begins processing it (showing the object the connector
receives from the collaboration object), and after the connector is done
processing the object (showing the object that the connector returns to the
collaboration object).
- Messages that comprise a business object dump.
- Methods that indicate individual method entry and exit points.
|
For more information on
tracing, including how to enable and set it, see the Connector
Development Guide for Java. For detailed information on
troubleshooting problems you may encounter when using the connector, see Appendix D, Retek connector problem determination.
