Real Time Information Director User Documentation

RTID Management
Hewlett-Packard Company 23 529618 - 001
Troubleshooting
This section provides an overview of the tools and resources you can use to troubleshoot
problems that might arise after you deploy your solution. It also recommends approaches
for addressing some typical types of problems.
T
T
o
o
o
o
l
l
s
s
a
a
n
n
d
d
R
R
e
e
s
s
o
o
u
u
r
r
c
c
e
e
s
s
The tools and resources available for troubleshooting your solution fall into several
categories:
• Error and event logs
• Error folder
• Statistics output
• Command-line tools and interfaces
E
E
r
r
r
r
o
o
r
r
a
a
n
n
d
d
E
E
v
v
e
e
n
n
t
t
L
L
o
o
g
g
s
s
Depending on the type of error that arises, you might have to consult any of the following
logs.
Server Log
The Director uses the WLS server log to report events and errors. There are four possible
log levels:
• INFO messages report expected events, such as the instantiation of a metadata
class, the creation of a document handler, or a change in the processing mode for
a source system.
• WARNING messages report conditions that might lead to errors, for example the
arrival of inbound document almost too large to process.
• ERROR messages describe processing failures resulting from invalid input,
metadata errors, database errors, and so on.
• DEBUG messages provide more detailed information about errors.
You use the management client or interface to set the log level, as described in “Setting
Log Level.”
An important element in ERROR and DEBUG messages is the exception category, which
reveals the source of the problem and implies a means of correcting it:
• An InvalidInputException requires the sending application to correct the data.