Summary

SmartSockets provides both peer-to-peer and client-server communications models (with the TipcConn and TipcSrv classes, respectively).

RTserver is a standard SmartSockets process used to implement the publish-subscribe communications services, allowing location transparency of RTclients.

An RTclient connects to a single RTserver. An RTserver process can connect to other RTservers. Messages are dynamically routed from an RTclient to other RTclients through one or more RTservers using a lowest cost algorithm.

RTserver is not started automatically by Java RTclients if it is not already running. RTserver can be started manually using the rtserver shell script. RTserver can be stopped manually using the rtserver shell script with the -stop command line argument.

	On platforms that support both 32- and 64-bit, use the rtserver64 command to run the 64-bit version of the rtserver script.

RTserver runs as a background (detached) process.

By default, a client program tries to connect to an RTserver process on its same node. A client program can connect to an RTserver on another node by setting the ss.server_names option.

The ss.project option is used by RTclients to prevent processes in another project from communicating with them.

Subjects are logical addresses set as the destination property of a message. Subjects are used by RTserver to dynamically route messages to all RTclients subscribed to that subject. This allows a single message to be delivered to multiple RTclients with a single operation.

Subjects are the fundamental unit used by SmartSockets to implement publish-subscribe services.

Subject names can be specified in a hierarchical manner, and to any number of levels, for example, /company/software/tibco.

Rather than deliver a message to all RTclients that have subscribed to a subject, a message can be delivered to only one of a set of RTclients using load balancing.

Load balancing can be set on a per-message or per-message-type basis.

Wildcards, asterisks (*) and ellipsis (...), can be used when subscribing or publishing to a subject.

Always be sure to call the TipcSrv’s destroy method before your program exits to disconnect from RTserver and flush any messages still in the buffer.