As part of the Express installation, you can choose to configure the Publisher API. You can identify data
channels to be used by the Publisher API, set the number of message buffers, and enter the JINI Server Host Name.
Publisher API configuration dialog 1
The Publisher API 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.
Publisher API dialog 1 configuration options
|
Field name
|
Default value
|
Description
|
|
Channel Name
|
Custom Channel 1
|
Identifies the data channel that Publisher
API uses to send messages to a subscriber. Although the installer
assigns Custom 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. Assigning unique names to channels can help you track
each one more easily in the event that an error is logged.
|
|
Local Interface
|
None
|
Identifies the IP address of the network
interface to which this channel will be bound. This allows a user
to bind various data channels to separate network interfaces to
enhance performance.
-
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 the Publisher API uses to multicast messages to subscribers.
This value should match the multicast address that the subscribers
use 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
|
3250
|
Identifies the local port on which this
data channel will operate.
Publishers can multicast messages to a subscriber on multiple data
channels that share the same local interface and Broadcast IP Address,
but the Broadcast Port must be unique to that 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 display a blank data channel dialog.
-
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.
Publisher API configuration dialog 2
For peak performance, you can tune the number of message buffers.
This dialog lets you set the number of message buffers.
Publisher API dialog 2 configuration options
|
Field name
|
Description
|
|
Number of message buffers
|
Identifies the number of packets the
subscriber temporarily stores to track data deliveries. Subscribers
track the number of packets delivered by a publisher. If a subscriber
suspects that a packet may be missing, it issues a resend request
to the publisher to retrieve the missing data.
|
Publisher API Configuration dialog 3
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 Publisher API with the JINI Server. The
JINI server host name is the same host machine where you install
Operations Console.
Publisher API dialog 3 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.
|