RAPCache Subscriber Configuration

Note:

If you install the RAPCache Subscriber at a different time than the RAPCache Database Server, the installer will prompt you for the server’s location. The RAPCache Subscriber must be installed on the same machine as the RAPCache Database Server.

RAPCache Subscriber configuration dialog 1

Operations Console communicates with the RAPCache Subscriber through an intermediary UAF agent. Use this dialog to set the UAF agent listening port and optional UAF component name.

Table 1. RAPCache Subscriber dialog 1 configuration options
Field name	Default value	Description
Listening Port	3401	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	Identifies the component. This name appears on the Operations Console Monitor. Although the Component Name is optional, naming the component 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 easily track them.

RAPCache Subscriber configuration dialog 2

This is an optional dialog that only appears if you install the RAPCache Subscriber separately from the RAPCache Database Server. Use this dialog to set the connection parameters to the RAPCache Database Server.

Table 2. RAPCache Subscriber dialog 2 configuration options
Field name	Default value	Description
Port	5000	Identifies the port that RAPCache uses to service connection requests. This value must match the port you defined when you installed the RAPCache Server.
User Name	RAP_USER	Identifies the default RAP user, `RAP_USER`. You may not change this value.

Note:

If you install the RAPCache server and RAPCache subscriber as a group, the server settings you have already defined automatically appear in this wizard.

RAPCache Subscriber configuration dialog 3

RAPCache Subscriber listens to one or more data channels for data sent by publishers. Use this dialog to identify each channel that you want RAPCache Subscriber to monitor.

Table 3. RAPCache Subscriber dialog 3 configuration options
Field name	Description
Channel Name	Identifies a specific data channel that a particular publisher uses to multicast messages to RAPCache Subscriber. The Channel Name depends on the data channel you want RAPCache Subscriber to monitor. If, for example, you want RAPCache Subscriber to monitor FAST Feed Handler, andkept all the defaults when you defined the FAST Feed data channels, you would use FAST Channel 1 as the first Channel Name. Subsequent channel names would matchthose of other data channel names.
Publisher Name	Identifies the publisher that sends messages to this subscriber. The Publisher Name can be any value. It is used to identify the publisher in the event that an error is logged.
Local Interface	Identifies the IP address of the network interface that the publisher uses to multicast messages to RAPCache Subscriber. This value must match the local interface value that the publisher uses to multicast messages. If you want RAPCache Subscriber to monitor a particular FAST Feed Handler data channel, for example, 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 multicast messages to RAPCache Subscriber. This value must match the multicast address that the publisher uses to multicast messages to RAPCache Subscriber. If you want RAPCache Subscriber to monitor a FAST Feed Handler data channel that multicasts messages on 224.0.2.0, for example, you would use that address for this field. All multicast IP addresses must range from `224.0.2.0` through `224.0.255.0`.
Broadcast Port	Identifies the port from which the publisher multicasts messages to RAPCache Subscriber. Publishers can multicast messages to a RAPCache 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 there is a checkmark in the I would like to define another data channel box to define another data channel.
Remove the checkmark in the I would like to define another data channel box, and click Next to display the next set of configuration options.

RAPCache Subscriber configuration dialog 4

RAPCache Subscriber listens for administrative requests from Operations Console. Use this dialog to set the administrative listening port and some performance options.

RAPCache Subscriber configuration dialog 3

Table 4. RAPCache Subscriber dialog 4 configuration options
Field name	Default value	Description
Administration Listening Port	3402	Identifies the listening port that the subscriber uses to monitor administrative requests (shutdown, restart, and refresh commands) from Operations Console.
Number of Packet Buffers	5000	Identifies the number of packet buffers. The subscriber holds onto arriving packets of messages until the packets are processed. The number of packet buffers is 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 setting if resend requests from publishers are failing, because the packet no longer exists. For subscribers, a value of 500 will usually provide sufficient buffering to handle small bursts of high-volume data.
Number of Packets Tracked	5000	Identifies the number of packets the subscriber tracks. If a subscriber suspects that a packet may be missing, it issues a resend request to the publisher to retrieve the missing data. The number of packets tracked is for each data stream.

RAPCache Subscriber configuration dialog 5

RAPCache Subscriber communicates with one or more publishers. Use this dialog to identify the publisher(s) you want RAPCache Subscriber to monitor.

Table 5. RAPCache 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. It 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. Used to connect to the publisher to request packet resends.
Resend Listener Port	Identifies the port on which 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.

Note:

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

Click Next, making sure there is a checkmark in the I would like to define another publisher box to define another publisher.
Remove the checkmark in the I would like to define another publisher box, and click Next to display the next set of configuration options.

RAPCache Subscriber configuration dialog 6

If you install the RAPCache Subscriber at a different time than the RAPCache Database Server, this optional dialog appears and prompts you for the server’s location. If you install the RAPCache Subscriber and the RAPCache Database Server at the same time, this screen is skipped.

Table 6. RAPCache Subscriber dialog 6 configuration options
Field Name	Default value	Description
RAPCache Server installation location	Defaults to the install machine name	Identifies the host name of the server where you installed the RAPCache Server. You can modify the name accordingly.

RAPCache Subscriber configuration dialog 7

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, the installer does not display this dialog.

If this dialog appears, you must identify the JINI server host name to register the RAPCache Subscriber with the JINI Server. The JINI server host name is the same host machine where you install Operations Console.

Table 7. RAPCache Subscriber dialog 7 configuration options
Field Name	Description
JINI Server Host Name	Identifies the host name of the server where the RAP JINI server resides. This is the machine on which Operations Console is installed.