Tracing determines what level of errors or warnings are captured
in the adapter log file. You can trace messages regarding adapter processing
by defining a tracing level. Trace messages, by default, are captured in the
adapter log file, but can be captured in a separate file if you prefer. (For
the enterprise service discovery wizard, the trace messages are captured in
the same file as that used for the wizard’s log messages.)
- Start the WebSphere® Process Server administrative console.
- From the administrative console, select .
- Select the Tracing level that you need. The “Tracing
levels” table describes the different tracing levels that can be set through
the WebSphere Process
Server administrative console.
Tracing levels
Level |
Indicator |
Description |
Fine |
1 |
General trace. Includes broad actions being taken by adapter
such as establishing a connection to the EIS, converting an event in the EIS
to a business object (only key values), processing a business object (only
key values). |
Finer |
2 |
Detailed trace that provides more granular information
on the logic being performed by the adapter including the various API calls
being made to the EIS and any parameters or return values. |
Finest |
3 |
This is the most detailed level and should include method
entry / exit / return values. Complete business object dumps should be included.
At this level, all detail needed to debug problems should be provided. |
- Click Apply to save your changes.
Terms of use |
Last updated: Thu 12 Oct 2006 03:34:40
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)