Tracing is an optional debugging feature you can turn on to closely follow
connector 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 for
Java.
Connector trace levels are as follows:
- Level 0
- This level is used for trace messages that identify the connector
version.
- Level 1
- Trace each time the pollForEvents method is called. Trace the TLO
name created by listeners for delivery to ICS. Trace the Request
business object name and the corresponding attribute name in the TLO.
- 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(). Also, trace which protocol handler
is processing the request.
- Level 3
- Trace the ASI of the business object being processed. Trace
attributes of the business object being processed. Trace the TLO of the
SOAP Request business object during event notification. Trace the
business object returned by the data handler.
- Level 4
- Trace the transport headers associated with:
- a SOAP request message retrieved by the protocol listener from the
transport
- a response message sent to the client by the protocol listener.
Trace the spawning of threads, all ASI that is processed, and all entries
and exits of important functions.
- Level 5
- Trace the following:
- the entries and exits for each important method
- all of the configuration-specific properties
- the loading of each of the protocol listeners
- the request message retrieved by the protocol listener from the transport
- the response message sent on the transport to the client by the protocol
listener
- the loading of each protocol handler
- the messages returned by the SOAP data handler
- business object dumps of the TLO sent to the collaboration
- dumps of the business objects returned by the data handler.
