Demo Subscriber Configuration

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

Demo subscriber dialog 1 configuration options
Field name	Default value	Description
Listening Port	3701	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 this 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 help you more easily track each item.

Demo subscriber listens to one or more data channels for messages sent by publishers. Use this dialog to identify each channel that you want demo subscriber to monitor.

Demo subscriber dialog 2 configuration options
Field name	Description
Channel Name	Identifies a specific data channel that a particular publisher uses to multicast messages to demo subscriber. The channel name depends on the data channel you want demo subscriber to monitor. For example, if you want demo 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 then match those of other data channel names.
Publisher Name	Identifies the publisher that sends messages to this subscriber, and 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 send multicast messages to demo subscriber. This value must match the local interface value that the publisher uses to multicast messages. For example, if you want demo 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 defined for FAST feed handler.
Broadcast IP Address	Identifies the Class D multicast IP address that the publisher uses to send multicast messages to demo subscriber. This value must match the multicast address that the publisher uses to send multicast messages to demo subscriber. For example, if you want demo 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 multicasts messages to demo subscriber. Publishers can send multicast messages to demo 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.

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

Demo subscriber dialog 3 configuration options
Field name	Default value	Description
Administration Listening Port	3702	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 arriving packets of messages until the packets 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. If resend requests from publishers are failing, this setting should be adjusted because the packet no longer exists at the publisher. The number of packet buffers should be between 80 to 90 percent of the number of packet buffers that publishers use.

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

Demo subscriber dialog 4 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. 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.

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.

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, you must identify the JINI server host name to register demo subscriber with the JINI server.

Demo subscriber dialog 5 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.