The Server_Names option specifies a list of logical connection names used to find and start an RTserver. Each logical connection name has either of these forms:
protocol:node:address
, which can be shortened to protocol:node
, protocol
, or node
pgm
:node:unicast_protocol.address
, used when the logical connection is for multicast, used by RTclients to connect to an RTgms processproxy
:node
:address
@protocol
:dest_node
:dest_address
, which is used when the logical connection to RTserver is through a proxy server (for example, a web proxy server with HTTP CONNECT enabled). For more information about valid protocols, nodes, and addresses, see Logical Connection Names for RT Processes. Note that the start prefix can only be used by an RTclient to start an RTserver. No other RT process can use it to start an RTserver, and an RTclient cannot use it to start any process other than an RTserver.
For an RTclient, RTmon, or RTgms process, this option is required and cannot be unset. An RTclient must establish a connection to either an RTserver or an RTgms. RTmon or RTgms processes must establish a connection to an RTserver. These connections are required to communicate with other SmartSockets processes.
RTgms creates multiple connections to the RTserver specified in Server_Names: a single control channel connection and one connection for each group that RTgms manages.
A logical connection name of pgm:localhost
does not connect to an RTgms process. If you want to use localhost
, you must also specify TCP in the logical connection name:
For an RTserver process, the logical connection names specified in Server_Names are used to find other RTserver processes. For an RTserver process, you can set Server_Names to UNKNOWN
, the default setting, and your RTserver process does not attempt to find any other RTservers.
TIBCO SmartSockets™ User’s Guide Software Release 6.8, July 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |