Specify where to store temporary market data files, assign data channels and publishers, and identify the JINI server host name.
The RAPStore subscriber temporarily writes market data messages to files. The location of these directories should match the values on your worksheet. These directories are automatically created during the installation.
Field name |
Description |
---|---|
Primary file location |
Identifies the directory where the subscriber temporarily writes market data messages before it loads the database. |
Overflow file location |
Identifies the directory where the subscriber stores temporary market data message files when the primary directory is full. |
RAPStore subscriber listens on one or more data channels for messages sent by publishers. Use this dialog to identify the data channels you want RAPStore subscriber to monitor.
Field name |
Description |
---|---|
Channel Name |
Identifies a specific data channel that a particular publisher uses to send multicast messages to RAPStore subscriber. The channel name depends on the data channel you want RAPStore subscriber to monitor. For example, if you want to RAPStore subscriber to monitor FAST feed handler, and kept all the defaults when you defined the FAST feed data channels, use FAST channel 1 as the first channel name. Subsequent channel names match those of other data channel names. |
Publisher Name |
Identifies the publisher that sends messages to this subscriber, in the event that an error is logged. |
Local Interface |
Identifies the IP address of the network interface that the publisher uses to send multicast messages to RAPStore subscriber. This value must match the local interface value that the publisher uses to send messages via multicast. For example, if you want RAPStore subscriber to monitor a particular FAST feed handler data channel, the local interface value you use here must match the local interface value for the data channel you defined for FAST feed handler. |
Broadcast IP Address |
Identifies the Class D multicast IP address that the publisher uses to send multicast messages to RAPStore subscriber. This value must match the multicast address that the publisher uses to send multicast messages to RAPStore subscriber. For example, if you want RAPCache subscriber to monitor a FAST feed handler data channel that sends multicast messages on 224.0.2.0, use that address for this field. All multicast IP addresses must range from 224.0.2.0 – 224.0.255.0. |
Broadcast Port |
Identifies the port from which the publisher sends multicast messages to RAPStore subscriber. Publishers can send multicast messages to a RAPStore subscriber on multiple data channels that share the same local interface and broadcast IP address, but the broadcast port must be unique to each data channel. |
The RAPStore subscriber communicates with one or more publishers. Use this dialog to identify the publishers you want the RAPStore subscriber to monitor.
Field name |
Description |
---|---|
Publisher Name |
Identifies the publisher that publishes to this subscriber, in the event that an error is logged. |
IP Address |
Identifies the IP address of the machine on which the publisher resides. This is used to connect to the publisher to request resends of packets. |
Resend Listener Port |
Identifies the port that the publisher uses to resend cached message packets to the subscriber. Publishers maintain a cache of recently sent message packets to ensure that the subscriber processes all message deliveries. |
Installing Operations Console also installs a JINI server that tracks RAP components. This dialog appears only if you install components separately. If you install multiple components at the same time, and previously identified the JINI server host name, this dialog does not appear.
If this dialog appears, you must identify the JINI server host name to register RAPStore subscriber with the JINI server.