Real Time Information Director User Documentation

RTID Extensibility
Hewlett-Packard Company 23
529618 - 001
Logging Related Properties
•
LogFileName
•
LogLevel
•
ErrorHandlerClass
•
SaveFilePrefix
•
SaveDirectory
Driver Arguments
All drivers use the same argument definitions for their operation, but not all argument
definitions are supported for all drivers. For instance, QueueSend, which reads in a file
and sends it to a JMS Queue doesn’t use the ‘–o outputDirectory’ option, because it
produces no output.
There are two types of arguments supported by the test drivers:
•
Configuration arguments, which set internal flags used when performing actions.
•
Action arguments, which cause the test drivers to perform some test action.
Because arguments are scanned in order, the set of arguments can be thought of as a
sequence of commands to the test driver. For example, the command
java –Dzli.propertyfile=zli.properties Dispatch –i inputDir –o
outputDir –z zipFile –i anotherInputDir anotherFile
first sets the input and output directories, then processes the zipFile from the input
directory inputDir, then changes the input directory, and finally processes the file
‘anotherFile’ from the ‘anotherInputDir’ directory.
Here’s another example to illustrate the significance of the order of arguments. The
following command loads a class called com.hp.rtsc.documents.NativeDelivery,
processes a document called DELIVERY, and stores the response XML message in a
directory called ‘verify’. It also exports, to ‘verify’, the schema for the NativeDelivery
document type and for each document type represented in the DOCCLASS table. Thus,
at the completion of the run, the ‘verify’ directory contains one response XML document
and many schema (.xsd) files.