RAPStore Subscriber XML Element Descriptions

Configure the RAPStore Subscriber using the three configuration files located in the RAPStoreSubscriber/config folder: opensubscriber.xml, messagefilter.xml and rapstore.xml. The RAPStore Subscriber Elements of rapstore.xml describe elements specific to the RAPStore Subscriber.

The contents of opensubscriber.xml and messagefilter.xml are identical to the DemoSubscriber’s configuration files.

The rapstore.xml file contains configuration information specific to the RAPStore Subscriber.

RAPStore Subscriber Elements of rapstore.xml
Element	Description
StoreDSH	Root element for the configuration file.
WorkDB	Gives the connection information for the RAPStore database and is used to persist information about files awaiting loading into the RAPStore Database.
WorkDBServer	Contains the name of the machine hosting the WorkDB database.
WorkDBPort	Contains the port number for WorkDB database.
WorkDBUser	Contains the user name for connecting to the WorkDB database.
WorkDBPassword	Contains the password for connecting to the WorkDB database.
StoreDB	Gives the connection information for the RAPStore database and is the database which used to store the messages processed by RAP.
StoreDBServer	Contains the name of the machine hosting the StoreDB database.
StoreDBPort	Contains the port number for StoreDB database.
StoreDBUser	Contains the user name for connecting to the StoreDB database.
StoreDBPassword	Contains the password for connecting to the StoreDB database.
PrimaryFileLocation	Points to a directory where the generated binary files (containing messages received from the publishers) can be written so that the messages can be loaded into the RAPStore database. The directory should be on a separate disk/controller from the RAPStore database devices and should have enough free space to hold any generated binary files that have not yet been loaded during the course of the day.
OverflowFileLocation	OverflowFileLocation is used only used when the PrimaryFileLocation is full. It should be on a separate disk/controller from both the RAPStore database devices as well as the PrimaryFileLocation.
IOBufferSizeMB	Specifies the size in megabytes of each internal IO Buffer used to store messages received from the publishers before the messages are written out to file. Each table referenced in the message templates has NumIOBuffers buffers created. Larger buffers can result in better throughput for writing the messages to disk, but also consumes more memory.
NumIOBuffers	Determines the number of IO Buffers created per table. This should have the value 3.
TargetFileSizeMB	Specifies the maximum size of a generated binary file in the file system. It should be a multiple of IOBufferSizeMB. Larger binary files require more memory in the RAPStore database and take longer to load.
IdleBufferWriteDelaySec	Specifies the number of seconds data can be present in an opened and idle generated binary file before being written out and made available for loading into the RAPStore Database.