RAPStore Subscriber Configuration

Note: By default, "Install Sample Message Templates" is selected; unselect the option to use RAPStore Subscriber only for data transfers and truncations.

Operations Console communicates with the RAPStore subscriber through an intermediary UAF agent that listens for requests. This dialog sets the UAF agent listening port and component name.

RAPStore subscriber dialog 1 configuration options
Field name	Default value	Description
Listening Port	3601	Identifies the listening port that the UAF agent uses to communicate with Operations Console. You can use any free port on your system.
Component Name	None	(Optional) Identifies the component. This name provides an identity that distinguishes this component from other components of the same type. Projects may include several subscribers or publishers. Assign unique component names to more easily track them.

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.

RAPStore subscriber dialog 2 configuration options
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.

RAPStore subscriber dialog 3 configuration options
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 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 would 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 subscriber uses to receive multicast messages from the publisher. 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 multicast messages to RAPStore subscriber. For example, if you want RAPCache subscriber to monitor a FAST feed handler data channel that sends multicasts messages on 224.0.2.0, use that address for this field. All multicast IP addresses must be in the range 224.0.2.0 – 224.0.255.0.
Broadcast Port	Identifies the port from which the publisher sends multicasts 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.

Note:

After you define the first channel, do one of the following:

Click Next, making sure that "I would like to define another data channel" is selected.
Unselect "I would like to define another data channel", and click Next to display the next set of configuration options.

The RAPStore subscriber listens to administrative requests from Operations Console. Use this dialog to identify the administration listening port and set some performance options.

RAPStore subscriber dialog 4 configuration options
Field name	Default value	Description
Administration Listening Port	3602	Identifies the listening port that the subscriber uses to monitor administrative requests from Operations Console.
Local Interface	Machine hostname	Identifies the local interface that the subscriber uses to monitor administrative requests.
Number of packet buffers	8000	Identifies the number of packet buffers. The subscriber holds onto messages packets until they are processed. The specified number of packet buffers are created per data stream. This setting can have a value between 1 and 4 billion, but the machine must have enough memory to hold the number of packets specified. Adjust this value if resend requests from publishers are failing because the packet no longer exists at the publisher. The number of packet buffers should be between 80 -- 90 percent of the total number of packet buffers that publishers use.

The RAPStore subscriber communicates with one or more publishers. Use this dialog to identify the publishers you want the RAPStore subscriber to monitor.

RAPStore subscriber dialog 5 configuration options
Field name	Description
Publisher Name	Identifies the publisher that publishes to this subscriber. The publisher name can be any value and is used to identify the publisher 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 this subscriber uses to request missing packets from the publisher.

Note:

After you define the first publisher, do one of the following:

Click Next, making sure that "I would like to define another publisher" is selected.
Unselect "I would like to define another publisher", and click Next to display the next set of configuration options.

If you install the RAPStore subscriber at a different time than the RAPStore database server, this optional dialog appears and prompts you for the server’s location. If you install the RAPStore subscriber and the RAPStore database server at the same time, this dialog does not appear.

RAPStore subscriber dialog 6 configuration options
Field name	Default value	Description
RAPStore Server location	Defaults to the install machine name	Identifies the location of the RAPStore database server. Specify this location to allow the subscriber to communicate with the database. This value defaults to the name of the machine where the install is running.

Installing Operations Console also installs a JINI server that tracks RAP components. This dialog only appears 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, identify the JINI server host name to register RAPStore subscriber with the JINI server.

RAPStore subscriber dialog 7 configuration options
Field name	Default value	Description
JINI Server Host Name	None	Identifies the host name of the server where the RAP JINI server resides. This is the machine on which Operations Console is installed. Identify the JINI Server Host Name to register this component with the JINI server.