WebSphere® Adapter
for Siebel Business Applications 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. Since 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
For the Siebel Adapter,
logging is enabled through the WebSphere Process Server Administrative Console.
Follow the steps below to enable the logging feature.
Steps for this task
- Start WebSphere Application Server.
- Start the WebSphere Process Server administrative console.
- Log into the WebSphere Process Server administrative console.
- From the administrative console, select .
- Click 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 that you need. The Logging
levels table below describes different logging levels that you can set through
the WebSphere Process
Server administrative console.
Note: To view detail-level log events,
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® Service log
(when enabled), or the Diagnostic Trace Service (when enabled).
Logging levels
Level |
Indicator |
Description |
Audit |
A |
Significant event affecting server state or resources |
Config |
C |
Configuration change or status. |
Detail |
D |
General information detailing subtask progress. |
Fatal |
F |
Task cannot continue. Component cannot function. |
Info |
I |
General information outlining overall task progress |
Severe |
E |
Task cannot continue. Component can still function. This also includes
conditions that indicate an impending fatal error - i.e. 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. |
- Click Apply to save your changes.