Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Fault Tolerance and Load Balancing in a EMS-Based Administration Domain : Creating a Secondary Administration Server

Creating a Secondary Administration Server
A secondary server can be added to an administration domain. The secondary server is equivalent to a primary server in that it has read and write permissions enabled. You can include or create additional secondary servers if a secondary is up and running. Secondary servers can be used for load balancing and fault tolerance.
Use this procedure to add a secondary server to an administration domain that uses TIBCO EMS as the transport.
To Add a Secondary Server Using the GUI
1.
Start Domain Utility and click the Next button on the main screen.
2.
Under Category, click Domain Configuration, then click Add a secondary server.
3.
Click Next and in the screen that appears:
Select Show Advanced and click TIBCO EMS as the transport. The EMS parameters must be defined for the secondary server.
Click the Discover button and select a domain. If a domain does not appear, select Show Advanced and increase the Discover Timeout value. The value sets the amount of time Domain Utility has to connect to the master server. If no connection is made in the specified time, the discovery operation will time out. Increase this number on slow systems and click the Discover button again.
Provide domain details. See Secondary Server Fields for field descriptions.
4.
Click the Next button. The screen that appears displays the ports used by the Web Server.
5.
Click the Next button Provide the administration credentials that were defined when the domain was created.
6.
Click the Next button. The screen that appears displays a summary of the values you have provided.
7.
Click the Next button to add the secondary server to the domain. After joining the domain, the services that support the secondary server are listed. You must start each service to enable the secondary server.
8.
Click Finish to end the session.
To Add a Secondary Server Using the Command Line Utility
1.
2.
Copy the following file to your working directory: TRA_HOME\template\domainutility\cmdline\AddSecondaryServer.xml
3.
Open AddSecondaryServer.xml in a text editor.
After changing the parameters, save the file and exit the text editor.
4.
   domainutilitycmd -cmdFile
                         working-dir-path\AddSecondaryServer.xml
Secondary Server Fields
 
Click Discover Domains to choose the domain for which you wish to install a secondary server.
The name of the machine is provided in the Machine field and must not be changed.
Machines are grouped in the Administrator GUI under the value provided in the Hawk Cluster field. If you change the default value, this machine displays in the Administrator GUI under the value you provide. The cluster name must be enclosed within quotes, if the name contains spaces.
Specify the user account name authorized to administer the TIBCO Enterprise Message Service server. Specify a user that is a member of the $admin group (for example, the predefined admin user), or a user who has the following permissions:
com.tibco.pof.domain-name.> (for each domain)>
com.tibco.pof.AUTH_domain-name.> (for each domain)
Note: You must add the following topics to the TIBCO_HOME/ems/bin/topics.conf file:
com.tibco.pof.domain-name.>
com.tibco.pof.AUTH_domain-name.>
_HAWK.domain-name (one line for each domain)
You must also add the following queue to the TIBCO_HOME/ems/bin/queues.conf file:
Note that if domain-name, contains the characters '.', '>' and '*', the characters must be replaced by the following strings:
Click the ... button and navigate to a drive shared by all nodes in the cluster. Specify the location of the TIBCO Runtime Agent domain home. For example, C:\tibco\tra\domain.
See the TIBCO Runtime Agent Installation guide for information about installing TIBCO software in a cluster environment.
Click the ... button and navigate to a drive shared by all nodes in the cluster. Specify the location of the administration server domain home. For example, C:\tibco\administrator\domain.
Select the Use default values check box unless you are an experienced user.
Note: This option does not affect sensitive data in the deployment configuration files exported using the AppManage utility. See TIBCO Runtime Agent Scripting Deployment Guide for information on how to protect sensitive data in the deployment of configuration files using an encryption password.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved