Copyright © TIBCO Software Inc. All Rights Reserved

Adding a Secondary Server to a Domain

Use this procedure to add a secondary server to an administration domain that uses TIBCO Rendezvous as the transport. The primary server for the domain must be running. The secondary server should be added to a machine on which the primary server is not installed.

A secondary server can be added to a cluster environment. Before adding the server, review the information about installing a master and secondary server in a cluster in TIBCO Runtime Agent Installing Into a Cluster.

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. It can be used for load balancing and fault tolerance.

The role of a secondary server depends on the domain transport you employ: • When you use TIBCO Rendezvous for your domain transport, secondary servers cannot deploy, undeploy, and delete applications like the primary server can. • When you use TIBCO Enterprise Message Service for your domain transport, secondary servers function exactly like the primary server and can deploy, undeploy, and delete applications.

To Add a Secondary Server Using the GUI

Once you have added a secondary server to a domain, you cannot promote it to a primary server.

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:

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.

Select Show Advanced if custom TIBCO Rendezvous parameters were specified for the master server. The same custom parameters must be defined for the secondary server.

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

Once you have added a secondary server to a domain, you cannot promote it to a primary server.

1.	Create a working directory that will hold the XML file that defines configuration options.

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.	Execute the following command to apply your changes to the domain:

   domainutilitycmd -cmdFile

   working-dir-path\AddSecondaryServer.xml

Secondary Server Fields

 

Table 19 Domain Details for Adding a Secondary Server

Domain Details
Administration Domain	Click Discover Domains to choose the domain for which you wish to install a secondary server.
Project Directory	Location in which the server looks for the domain data store, for project files saved as single-file projects, and for deployment configuration files.
Machine	The name of the machine is provided in the Machine field and must not be changed.
Hawk Cluster	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.
Advanced Options
Show Advanced	If you specified custom TIBCO Rendezvous parameters for the master server, click this check box, to specify the same custom parameters for the secondary server.
Discover Timeout	Time Domain Utility allows for connecting to the master server. If no connection is made in the specified time, the master server may be down or slow to respond and Domain Utility times out. Increase this number on slow systems.
TIBCO Rendezvous TIBCO EMS	Select the transport to use for administration domain communication. When adding a machine, you must select the transport already set for the primary domain. The fields change, depending on the transport selection. On selecting TIBCO EMS, you can edit the Hawk HMA parameters.
TIBCO Rendezvous parameters for TIBCO Administrator
RV Daemon	TIBCO Rendezvous Daemon used for client-server communication. Default is tcp:7500.
RV Network	TIBCO Rendezvous network used for client-server communication. This variable need only be set on computers with more than one network interface. If specified, the TIBCO Rendezvous daemon uses that network for all outbound messages.
RV Service	TIBCO Rendezvous service used for client-server communication. The Rendezvous daemon divides the network into logical partitions. Each transport communicates on a single service. A transport can communicate only on the same service with other transports. Unless you are using a non-default TIBCO Rendezvous configuration, you should use the default (7500).
TIBCO Rendezvous parameters for TIBCO Hawk
Hawk Daemon	TIBCO Rendezvous Daemon used for communication with TIBCO Hawk. Default is tcp:7474. See the TIBCO Hawk Installation and Configuration manual for details about this parameter.
Hawk Network	TIBCO Rendezvous network used for communication with TIBCO Hawk. Use the default unless you are an experienced TIBCO Rendezvous user. See the TIBCO Hawk Installation and Configuration manual for details about this parameter.
Hawk Service	TIBCO Rendezvous service used for communication with TIBCO Hawk. Use the default unless you are an experienced TIBCO Rendezvous user. Default is 7474. See the TIBCO Hawk Installation and Configuration manual for details about this parameter.
TIBCO EMS parameters for TIBCO Administrator
Server URL	The URL of the TIBCO Enterprise Message Service server in the following format: tcp://hostname:port. If you have configured multiple fault tolerant servers, specify all of them here, separating them by commas. For example: tcp://host1:7222,tcp://host2:7222
Username	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: • publish, subscribe, and create permissions to the following topics: com.tibco.repo.> com.tibco.pof> or com.tibco.pof.HawkConfig.> com.tibco.pof.MonitoringManagement.> com.tibco.repo.server_discovery.> com.tibco.pof.domain-name.> (for each domain)> com.tibco.pof.AUTH_domain-name.> (for each domain) com.tibco.repo.instance_mgmt.*.trustworthy_HAWK.domain-name (for each domain) • public, subscribe, and create permissions to the com.tibco.repo.> queues Note: You must add the following topics to the TIBCO_HOME/ems/bin/topics.conf file: com.tibco.pof.domain-name.> com.tibco.repo.server_discovery.> com.tibco.pof.AUTH_domain-name.> com.tibco.repo.instance_mgmt.*.trustworthy _HAWK.domain-name (one line for each domain) You must also add the following queue to the TIBCO_HOME/ems/bin/queues.conf file: com.tibco.repo.> Note that if domain-name, contains the characters '.', '>' and '*', the characters must be replaced by the following strings: "." replaced by "2E" ">" replaced by "3E" "*" replaced by "%2A"
Password	Specify the password for the user account given in the Username field.
Enable SSL	Select to enable Secure Sockets Layer (SSL) for use with TIBCO Enterprise Message Service. See Enabling SSL for a TIBCO Enterprise Message Service Domain for information about using SSL.
Domain Home Paths Configuration
TRA Domain Home	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.
Administration Domain Home	Specify the location of the administration server domain home. For example, C:\tibco\administrator\domain.
TIBCO Rendezvous parameters for TIBCO Hawk HMA
Use default values	Select the Use default values check box unless you are an experienced user.
Hawk HMA Daemon	Hawk HMA Daemon instructs the transport creation function about how and where to find the Rendezvous daemon and establish communication. The default is tcp:7474.
Hawk HMA Network	Hawk HMA Network specified, uses the specified network for all the communications.
Hawk HMA Service	Hawk HMA Service is used for client-server communication. Each transport communicates on a single service. A transport can communicate only on the same service with other transports. The default is 7475.
Cluster Group Configuration
Machine is Logical	Select to specify that the machine is a node in a cluster.
Virtual IP Address	Enter the cluster virtual IP.
Symmetric Key
Dynamic Symmetric Key	Select to use dynamically generated keys to encrypt sensitive data by default when deploying applications locally. A static key is used if this checkbox is cleared. 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.
Property Files Group Name
Authorized Group Name	This property is used to secure the .properties files. The specified group will be given view access to the AuthorizationDomain.properties and AdministrationDomain.properties files when these property files are created as part of domain creation. Specifying this property allows you in the specified group to use TRA utilities like AppManage.

Copyright © TIBCO Software Inc. All Rights Reserved