Real Time Information Director User Documentation

RTID Management
Hewlett-Packard Company 20 529618 - 001
The source is either the name of the source system to which the mode applies, or the
value SYSTEM to signify that the mode applies to all source systems. The mode can
have any of the values described in the next several paragraphs.
The default processing mode is OPEN, unless a different default mode is specified in the
properties file. In this mode, incoming documents are processed by the Director and
inserted appropriately into the data store.
CLOSED_DEFER mode saves each incoming document in a file for later processing.
Files are saved in the OSS error folder. The Director returns a response of 200,
indicating success. No entry is written to the server log. This option is used to capture
documents while troubleshooting mapping errors, making it unnecessary for the source
system to resend the documents.
CLOSED_NOERROR mode discards each incoming document. The Director returns a
response of 200, indicating success. No entry is written to the server log. This option is
useful for testing—it confirms, for example, that documents are being received—but
presumes that the data need not be inserted into the data store.
CLOSED_ERROR mode rejects each incoming document and sends an error response of
500 with a ProcessingClosed exception. No entry is written to the server log. This
option is an alternative to CLOSED_DEFER but presumes that the source system or
systems can later resend the documents.
S
S
e
e
t
t
t
t
i
i
n
n
g
g
t
t
h
h
e
e
D
D
o
o
c
c
u
u
m
m
e
e
n
n
t
t
H
H
a
a
n
n
d
d
l
l
e
e
r
r
Q
Q
u
u
o
o
t
t
a
a
A document handler is a class created to service documents of a particular type. Update
document handlers service requests to insert or update data in the data store. Query
document handlers service queries and subscriptions. A document handler has a JDBC
connection and some number of prepared JDBC statements, as dictated by the metadata
for the document type.
After creating a document handler, the Director prepares it by compiling the SQL
prepared statements for the document type.
When a handler is allocated to process a specific document, it is set to be in use (and
becomes one of the handlers reflected in the DocumentHandlerInUse statistic). After
processing a document, the handler is released into the pool of handlers that are not in
use and therefore available to service requests.
If you don’t set a quota on document handlers, a handler and its connection remain
available to service requests until the Director detects a database change. As the number
of document handlers increases with the transaction load, so does the number of database
connections held by a Director process. SQL/MX errors can begin to occur and
eventually abort the JVM. To prevent such occurrences, the Director lets you specify a