Configuring Fault-Tolerant Servers


To configure an EMS server as a fault-tolerant backup, set these parameters in its main configuration file (or on the server command line):

When the backup server starts, it attempts to connect to the primary server. If it establishes a connection to the primary, then the backup server enters standby mode. If it cannot establish a connection to the primary, then the backup server assumes the role of the primary server (in active mode).

While the backup server is in standby mode, it does not accept connections from clients. To administer the backup server, the admin user can connect to it using the administration tool.

Authorization and Fault-Tolerant Servers

EMS authorization interacts with fault tolerance. If authorization is enabled, then both servers in a fault-tolerant pair must have the same server name (that is, the server parameter in tibemsd.conf). Furthermore, you must add that server name as a user in the configuration file users.conf.

SSL

You can use SSL to secure communication between a pair of fault-tolerant servers.

Parameters in the main configuration file (tibemsd.conf) affect this behavior; see Fault Tolerance Parameters. The relevant parameters all begin with the prefix ft_ssl. You must configure these parameters for both servers in the pair.

See Also

Chapter 12, Using the SSL Protocol

Reconnect Timeout

When a backup server assumes the role of the primary server during failover, clients attempt to reconnect to the backup server (that is, the new primary) and continue processing their current message state. As each client reconnects, the backup server reads its message state from the shared state files.

You can instruct the server to clean up state information for clients that do not reconnect before a specified time limit.

The ft_reconnect_timeout configuration parameter specifies that time limit (in seconds). The default value is 60 seconds. See also, Fault Tolerance Parameters.


TIBCO Enterprise Message Service™ User’s Guide
Software Release 4.3, February 2006
Copyright © TIBCO Software Inc. All rights reserved
www.tibco.com