If you choose to configure RAPCache Subscriber, the installer displays several configuration dialogs.
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.
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 to RAPCache Subscriber to monitor FAST Feed Handler, and kept 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 match those 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. |
RAPCache Subscriber communicates with one or more publishers. Use this dialog to identify the publisher(s) you want RAPCache Subscriber to monitor.
Field name |
Description |
---|---|
Publisher Name |
Identifies the publisher that publishes to this subscriber. 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. 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 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.