Tracing

Tracing is an optional debugging feature you can turn on to closely follow connector behavior. Trace messages, by default, are written to STDOUT. Tracing properties are set with the standard configuration properties AgentTraceLevel, TraceFileName, and ControllerTraceLevel. For more on configuring trace messages, refer to Appendix A, "Standard configuration properties for connectors".

Table 7 shows the type of information you will receive for different tracing levels .

Table 7. Tracing messages content

Level Description
Level 0 Identifies the connector version. No other tracing is performed at this level.
Level 1
  • Provides status information.
  • Provides key information on each business object processed.
  • Records each time polling occurs.

Level 2
  • Identifies the business object handler used for each object that the connector processes.
  • Logs each time a business object is posted to the integration broker.
  • Indicates each time a request business object is received.

Level 3
  • Identifies the foreign keys being processed, if applicable. These messages appear when the
    connector has encountered a foreign key in a business object or when the connector sets a
    foreign key in a business object.
  • Business object processing. Examples of this include finding a match between business
    objects, or finding a business object in an array of child business objects.

Level 4
  • Identifies application-specific information. Examples of this include the values returned by
    the methods that process the application-specific information fields in business objects.
  • Identifies when the connector enters or exits a function. These messages help trace the
    process flow of the connector.
  • Records any thread-specific processing. For example, if the connector spawns multiple
    threads, a message logs the creation of each new thread.

Level 5
  • Indicates connector initialization. This type of message can include, for example, the value of
    each connector configurator property that has been retrieved from the broker.
  • Details the status of each thread that the connector spawns while it is running.
  • Represents statements executed in the application. The connector log file contains all
    statements executed in the target application and the value of any variables that are
    substituted, where applicable.
  • Records business object dumps. The connector provides a text representation of a business
    object before it begins processing (showing the object that the connector receives from the
    collaboration) as well as after it finishes processing the object (showing the object that the
    connector returns to the collaboration).

Copyright IBM Corp. 1997, 2004