Real Time Information Director User Documentation
RTID Management
Hewlett-Packard Company 25 529618 - 001
The Director can accumulate and report various statistics, including counts of SQL
operations, documents processed or serialized, and time spent in specific types of
operations.
You can use the management client to set statistics gathering options. For example, you
can isolate statistics pertaining to a document type or have statistics reported on a table-
by-table basis. For more information about the statistics gathering options, see “Setting
Statistics Gathering Options,” in this document.
You can also use the client to display statistics or harvest statistics to a file, as described
in “Director Management Client.”
C
C
o
o
m
m
m
m
a
a
n
n
d
d
-
-
l
l
i
i
n
n
e
e
T
T
o
o
o
o
l
l
s
s
a
a
n
n
d
d
I
I
n
n
t
t
e
e
r
r
f
f
a
a
c
c
e
e
s
s
In addition to the Management Client described in this document, you might need to use
a variety of other tools in the course of troubleshooting.
Director Test Drivers
Director test drivers are intended mainly for use in testing metadata and are therefore
described in the RTID Extensibility module, rather than here. But, of course, if you are
troubleshooting a metadata error, you’ll want to use a test driver to try out your fix.
Another case in which you might want to use a test driver for troubleshooting is to
research an apparent problem in HTTP communications; one of the scenarios discussed
in the next few pages includes this approach.
UNIX Tools
The Open Systems Services (OSS) environment makes available a set of tools familiar to
users of UNIX:
• grep to look for a particular string
• tail to look at the most recent entries in a log
• diff to compare a known good output with a current output
• offender to examine CPU and memory utilization
• viewsys to discover queue lengths
• XML Spy to look at metadata
T
T
r
r
o
o
u
u
b
b
l
l
e
e
s
s
h
h
o
o
o
o
t
t
i
i
n
n
g
g
S
S
c
c
e
e
n
n
a
a
r
r
i
i
o
o
s
s
How do we become aware that an error has occurred? Perhaps downstream users report
that data is missing from the data store, or a client reports that it can’t seem to submit
inbound documents. Or perhaps an operator monitoring the server log or the EMS log
notices a suspicious series of errors and warnings. This section describes approaches for
dealing with problems that surface in each of these ways.