Real Time Information Director User Documentation

RTID Extensibility
Hewlett-Packard Company 33
529618 - 001
Example:
java -Dzli.propertyFile=my.properties QueueReceive -q rtsc.TestQueue -o test/testOut
Listens to the JMS Queue named rtsc.TestQueue and puts all messages received on the
queue to the test/testOut directory
QueueSend Driver
This driver sends the specified input file(s) to the specified JMS Queue.
This driver generates no output files.
For syntax information, see the Javadoc for QueueSend.
Example:
java -Dzli.propertyFile=my.properties QueueSend –u 11.22.33.44:7001 -q rtsc.TestQueue
-d test/testIn
Processes all the files in the test/testIn directory, posting each one to the JMS Queue
named rtsc.TestQueue
Interactive Testing Using the Harness Driver
Testing of Director metadata has two major goals: to validate document definitions, and
to make sure that the results of submitting the corresponding documents are consistent
with expectations.
The Director validates metadata automatically when you start the server or run a test
driver. Specifically, the document definitions listed in the DOCCLASS table are loaded
and validated before use. Any metadata inconsistency results in a MetadataInconsistency
exception.
The second kind of testing involves submitting input files that contain either documents
for insertion or queries to retrieve information from the database. In such cases, the
objective is to validate the outputs or the contents of the database, rather than to look for
exceptions, but if any exceptions are generated, an error message indicates what action to
take to resolve the exception.
The Harness driver provides an interactive way to do both kinds of testing. In the case of
a new metadata class that isn’t yet in the DOCCLASS table, the Harness makes it
unnecessary to keep running a test driver that validates metadata listed in DOCCLASS.
When testing with XML files, the Harness makes it possible to generate the output XML
without repeatedly validating the same metadata.