Real Time Information Director User Documentation

RTID Management
Hewlett-Packard Company 26 529618 - 001
D
D
o
o
w
w
n
n
s
s
t
t
r
r
e
e
a
a
m
m
U
U
s
s
e
e
r
r
R
R
e
e
p
p
o
o
r
r
t
t
s
s
M
M
i
i
s
s
s
s
i
i
n
n
g
g
D
D
a
a
t
t
a
a
If a user of the data store reports that expected data is missing, proceed as follows:
1. Try to discover what the source system should have been, and find out whether a
whole document or only some data is missing.
2. If the whole document is missing, verify that the Director received and
processed the document:
• Examine the server log, which contains an entry for every document processed,
and see whether that document is reflected in the log; if there is an entry, look
for any report of an exception.
• If the server log doesn’t contain an entry for the document, check the access log.
If there is no entry in the access log, the document was never received. If there
is an entry, look at the success status; if it’s empty, the Director received a zero-
byte document from the source system, and you’d best notify the party
responsible for the source system.
• A lot of information recorded in the server and access logs in consolidated in the
transaction log, so you can also do a query on that table to see the status of the
load.
3. If only certain data from the document is missing, it is likely that the document
definition does not map all necessary fields. In this case, the person responsible
for maintaining the metadata needs to take a closer look at the metadata for the
document type.
T
T
h
h
e
e
C
C
l
l
i
i
e
e
n
n
t
t
o
o
r
r
S
S
o
o
u
u
r
r
c
c
e
e
S
S
y
y
s
s
t
t
e
e
m
m
R
R
e
e
p
p
o
o
r
r
t
t
s
s
a
a
P
P
r
r
o
o
b
b
l
l
e
e
m
m
If the client or source system reports a problem, proceed as follows:
1. If documents are being consistently rejected, examine the server log. One reason
for such a problem might be that no document definition matches the document
submitted. Check the exception reported in the log, and make sure the correct
document definition is deployed and reflected in the DOCCLASS table. If not,
deploy the necessary metadata class to the documents directory, then use the
management client to load the metadata dynamically. For information about
dynamically loading metadata, see “Dynamically Loading Document Metadata.”
2. If processing is slow, the problem might have to do with a sudden increase in
load from the client, or perhaps the presence of very large documents.
Remember that you can use the management client to set warning and abort
thresholds based on document size; you can adjust those numbers upward to
accommodate larger documents, or downward to provide notification of, or to
exclude them.
3. Review the provision for load balancing in parallel TCP/IP and/or NonStop
WLS.
4. If processing has stopped altogether, check the server log to make sure that
Director processes are running, and the EMS log to make sure that TCP/IP is