RAPStore subscriber options entered on the Subscribers Configuration page update XML elements in the rapstore.xml and opensubscriber.xml configuration files.
Option | Description |
---|---|
Login Name |
User name for connecting to the RAPStore database. |
Login Password |
Password for connecting to the RAPStore database. |
Server Hostname |
Name of the machine hosting the RAPStore database. |
Server Port |
Port number for RAPStore database. |
Option | Description |
---|---|
Login Name |
User name for connecting to the RAPStore database. |
Login Password |
Password for connecting to the RAPStore database. |
Server Hostname |
Name of the machine hosting the RAPStore database. |
Server Port |
Port number for RAPStore database. |
Option | Description |
---|---|
Primary File Location |
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 different disk/controller than 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. |
Overflow File Location |
OverflowFileLocation is used only used when the PrimaryFileLocation is full. It should be on a different disk/controller than both the RAPStore database devices and the PrimaryFileLocation. |
IO Buffer Size (MB) |
Specifies the size, in megabytes, of each internal I/O 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 may result in better throughput for writing the messages to disk, but also consumes more memory. |
Number of IO Buffers |
Determines the number of I/O buffers created per table. Use the value of 3. |
Target File Size |
Specifies the maximum size of a generated binary file in the file system. The file size should be a multiple of the I/O buffer size. Larger binary files require more memory in the RAPStore database and take longer to load. |
Idle Buffer Write Delay |
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. |
Buffer Age Limit (seconds) | Forces the loading of any data which has been in existence longer than the time limit. The default value for this parameter is 600 (10 minutes). This value must be 1 - 65535. |
Log Level |
The level of logging. Valid values are:
|
Log File |
Name and location of the log file. The file name can be relative or a full path. |
Template Directory |
Message template location. |
Number of Packet Buffers |
Number of network packet buffers to create per data channel. The size of one buffer is approximately the size of the Maximum Transmission Unit of the network interfaces being used. A larger number of packet buffers means that a larger burst of traffic can be handled without requiring resends. This setting can have a value from 1 - 4294967296. |
Packet Window Size |
Determines how many packets are tracked for resend purposes. This setting can have a value from 1 - 4294967296. The value should be 80 - 90% of the publishers NumPacketBuffers. |
Latency Check Interval (seconds) |
Determines in seconds how often the network latency between publisher and subscriber is checked. This setting can have a value from 1 - 65535. |
Flush Interval (ms) |
Indicates in milliseconds how long a data channel can sit idle before a check is made for dropped packets. This setting can have a value from 1 - 65535 |
Local Interface | Local interface that the publisher uses to monitor administrative requests. |
Admin Port |
Port number used by the UAF agent to communicate with the subscriber. The subscriber listens for incoming administration requests on this port. |
Max Connections |
Determines the number of concurrent connections to the AdminChannel. Defaults to 10. Value must be in the range of 1 - 65535. |