The WebSphere(R) Adapter for JDBC maintains a log file
that you can view to determine the status of event processing. All events
and errors that relate to the adapter are tracked by the log file, along with
the date, time, and event for each log entry. Because the adapter logs an
error message when it encounters an error or warning condition, the log file
is a good source to start troubleshooting problems.
Why and when to perform this task
The adapter communicates with the database through a JDBC driver,
and the SQL queries or stored procedure calls could result in an SQLException
message. These are captured and logged and a ResourceException message is
produced. Messages are returned based on errors occurring during request
processing or errors in the Event Store. Errors in event processing are handled
by the Event Manager.
Note: When you create and bind both an inbound
and outbound operation to the same adapter instance with the same AdapterID
property, you need to use the same log name, because only one log file will
be created once you deploy the adapter to WebSphere Process Server.
If the inbound and outbound operations belong to different adapters, each
with a different AdapterID, then a separate log file will be created for each
operation.
Logging for the adapter is enabled through the WebSphere
Process Server administrative console. Follow the steps below to enable logging.
Steps for this task
- Start logging and tracing
Start the WebSphere Process
Server administrative console. From the administrative console, select .
- Specify log detail level
Click either Component to
specify a log detail level for individual components, or click Groups to
specify a log detail for a predefined group of components.
- Select the logging level
The "Logging levels" table
describes the different logging levels that you can set through the administrative
console.
Note: To view log events that are below the Detail level,
you must enable the Diagnostic Trace Service. Log events that are at Detail
level or above can be viewed in the SystemOut log, the IBM(R) Service
log (when enabled), or the Diagnostic Trace Service (when enabled).
Logging levels
Level |
Indicator |
Description |
Fatal |
F |
Task cannot continue. Component cannot function. |
Severe |
E |
Task cannot continue. Component can still function. This also includes
conditions that indicate an impending fatal error, that is, reporting on situations
that strongly suggest that resources are on the verge of being depleted. |
Warning |
W |
Potential error or impending error. This also includes conditions
that indicate a progressive failure, for example, the potential leaking of
resources. |
Audit |
A |
Significant event affecting server state or resources. |
Info |
I |
General information outlining overall task progress. |
Config |
C |
Configuration change or status. |
Detail |
D |
General information detailing subtask progress. |
- Save logging information
Click Apply to
save your changes.