Elements of rapstore.xml

Element

Description

StoreDSH

Root element for the configuration file.

WorkDB

The WorkDB section gives the connection information for the RAPStore database and is used to persist information about files awaiting loading into the RAPStore Database.

WorkDBServer

This parameter contains the name of the machine hosting the WorkDB database.

WorkDBPort

This contains the port number for WorkDB database.

WorkDBUser

This contains the user name for connecting to the WorkDB database.

WorkDBPassword

This contains the password for connecting to the WorkDB database.

StoreDB

The StoreDB section gives the connection information for the RAPStore database and is the database which used to store the messages processed by Sybase RAP.

StoreDBServer

This parameter contains the name of the machine hosting the StoreDB database.

StoreDBPort

This contains the port number for StoreDB database.

StoreDBUser

This contains the user name for connecting to the StoreDB database.

StoreDBPassword

This contains the password for connecting to the StoreDB database.

PrimaryFileLocation

This parameter should point 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. It should have enough free space to hold any generated binary files that have not yet been loaded during the course of the day.

OverflowFileLocation

The 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

This parameter specifies the size in megabytes of each internal IO Buffer which is 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

This parameter determines the number of IO Buffers created per table. This should have the value 3.

TargetFileSizeMB

This 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

This parameter specifies the number of seconds data can be present in an opened and idle generated binary file before it is written out and made available for loading into the RAPStore Database.