Used for:
|
RTserver and RTgms only
|
Type:
|
String List
|
Default Value:
|
For RTserver:
For RTgms:
|
Valid Values:
|
Any valid logical connection name or names, separated by commas (,)
|
The Conn_Names option specifies a list of logical connection names used by RTclient processes and other RTserver processes to find this RTserver or used by RTclient processes to find this RTgms process. Each logical connection name has either of these forms:
protocol:node:address
, which can be shortened to protocol:node
, protocol
, or node
, for most normal connections to an RTserver
When protocol
is tcp
or a TCP-based protocol on a multi-homed machine, you can set node
to either of these keywords:
_node
|
causes RTserver to listen only on the default IP address for the machine.
|
_any
|
causes RTserver to listen on all IP addresses for the machine.
|
pgm
:node:unicast_protocol.address
, used when the logical connection is for multicast, to enable RTclients to find this RTgms
proxy
:node
:address
@protocol
:dest_node
:dest_address
, which is used when the logical connection is through a proxy server (for example, a web proxy server with HTTP CONNECT enabled) to the RTserver. The logical connection names are separated by commas (,). For more information about valid protocols, nodes, and addresses, see Logical Connection Names for RT Processes.
This option is required and cannot be unset.
![]() |
Using the keyword
_any in Conn_Names is discouraged for RTserver to RTserver connections. When an RTserver connects to another RTserver whose Conn_Names use _any , the RTserver might attempt to reconnect every Server_Reconnect_Interval seconds. This is a known problem and will be fixed in a future release.
|
TIBCO SmartSockets™ User’s Guide Software Release 6.8, July 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |