FAST Feed Handler Configuration

The configurable properties of the FAST Feed Handler include UAF port settings, FAST feed parameters, data channel assignments, listening port settings, and the JINI server host name.

FAST Feed Handler configuration dialog 1

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


ffhandlerinstall1

Table 1. FAST Feed Handler dialog 1 configuration options

Field Name

Default value

Description

Listen Port

3101

Identifies the UDP Local listening port for incoming messages.

Component Name

None

Identifies this component. This name appears in the component’s panel on the Operations Console Monitor. Naming the component provides an identity that distinguishes this component from other components of the same type. Projects may include several subscribers or publishers. Track items easier by assigning unique component names to them.

FAST Feed Handler configuration dialog 2

FAST Feed Handler listens for FAST messages sent by a FAST feed. This dialog prompts you for the FAST feed parameters.


ffhandlerimage2

Table 2. FAST Feed Handler dialog 2 configuration options

Field Name

Default value

Description

Listen Host IP Address

None

Identifies the IP address for a network interface to which the incoming feed's UDP channel will be bound. Network resources are optimized since the various channel loads are allowed to be spread out among multiple physical network adapters.

Listen Port

3170

Identifies the UDP Local listening port for incoming messages.

Multicast Host IP Address

224.0.255.0

Identifies the class D (multicast) IP address on which this data channel will operate.

A publisher can multicast messages to a subscriber on multiple channels, and the combination of the Broadcast IP Address and Broadcast Port must be unique for each channel. All multicast IP addresses must range from 224.0.2.0 through 224.0.255.0.

FAST Feed Handler configuration dialog 3

FAST Feed Handler multicasts messages to subscribers over one or more data channels. Four channels are recommended for a system that handles 300,000 messages per second. Use this dialog to identify the data channels.


ffhandlerinstall3

Table 3. FAST Feed Handler dialog 3 configuration options

Field name

Default value

Description

Channel Name

FAST Channel 1

Identifies the data channel that FAST Feed Handler uses to send messages to a subscriber. Although the installer assigns FAST Channel 1 to the first data channel by default, you can use any value as the channel name.

You must supply a Channel Name to any subsequent data channels you define. Track Channel Names more easily in teh event that an error is logged by assigning unique names to channels .

Local Interface

None

Identifies the IP address of the network interface to which this channel will be bound. Enhance performance by binding various data channels to separate network interfaces.


  • If you plan to install all publishers and subscribers on the same server, you must configure the Local Interface to use the loopback interface (127.0.0.1).

  • If you install publishers and subscribers on different servers, use the local machine address of the secondary Ethernet network card installed by the system administrator.

Broadcast IP Address

224.0.2.0

Identifies the Class D multicast IP address that FAST Feed Handler uses to multicast messages to subscribers. This value should match the multicast address that the subscriber uses to receive messages.

Although the installer assigns 224.0.2.0 as a default multicast IP address to all Broadcast IP address fields, your Network Administrator can choose an alternate multicast address. All multicast IP addresses must range from 224.0.2.0 through 224.0.255.0.

Broadcast Port

3150

Identifies the local port on which this data channel will operate.

Publishers can multicast messages to a subscriber on multiple data channels. Data channels can share the same local interface and Broadcast IP Address values, but the Broadcast Port must be unique for 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.

FAST Feed Handler configuration dialog 4

FAST Feed Handler listens for administrative requests from Operations Console and resend requests from subscribers. Use this dialog to set different listening ports and performance options.


ffhandlerinstall4

Table 4. FAST Feed Handler dialog 4 configuration options

Field name

Default value

Description

Administration Listening Port

3102

Identifies the listening port that the publisher uses to monitor administrative requests (including shutdown, restart, and refresh commands) from Operations Console.

Resend Listening Port

3103

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.

Number of packet buffers

10000

Identifies the number of packet buffers. The publisher 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. This setting should be adjusted if resend requests from publishers are failing, because the packet no longer exists at the publisher.

For the publisher, a value of 10000 will usually provide sufficient packet history to maintain data integrity under moderate loads.

FAST Feed Handler configuration dialog 5

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 theJINI 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 Publisher API with the JINI Server. The JINI server host name is the same host machine where you install Operations Console.


ffhandlerinstall5

Table 5. FAST Feed Handler dialog 5 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.


Created April 9, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com