Real Time Information Director User Documentation

RTID Deployment
Hewlett-Packard Company 20 529618 - 002
Start / Stop Load-Balanced Directors
Use the instructions for starting the Director as a generic process to start the individual
Director instances. As you can see from the STDOUT, each Director instance is listening
on two ports (the shared port and the management port).
Use the stop.sh script to stop the individual Director instances.
Appendix: Director Properties File
Configuration properties used by Director components are specified in a Java properties
file. By default, the filenames is zli.properties, but you can specify a different file name.
You include the properties file in the WLS domain folder and specify its name in the
setenv.sh script. You also specify the properties file on the command line when you run
an RTID test driver, as in the following example:
java –Dzli.propertyFile=myProperties QueueSend arguments
Additional properties are required if you wish to use subscriptions. Those properties are
described in the document entitled RTID Subscriptions.
Notice that two properties, the SQL catalogue name and the SQL schema name, must
have values specified in uppercase. Case is not significant for other properties.
Properties Related to Input File Processing
ABORT_THRESHOLD
Maximum number of start tags permissible in an input XML message. If the number of
start tags in a document exceeds the threshold, the Director rejects the document with an
InvalidInputException.
This property is read and initialized during startup; it can be overridden by the –at option
specified to the Management Client.
If you don’t specify a value, the threshold value is 2
63
– 1.
CheckDocumentSequence
Boolean value signifying whether the Director should check to see whether an incoming
document is out of sequence (has an earlier timestamp than the value currently stored in
the data store. Permissible values are “true” and “false”. The value is case insensitive
and does not include the quotation marks.