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


Chapter 2 Fault Tolerance and Load Balancing in a Rendezvous Administration Domain : Administration Domain Spanning Subnets

Administration Domain Spanning Subnets
You can extend an administration domain to span subnets by using the TIBCO Rendezvous routing daemon (rvrd).
TIBCO Administrator does not provide built-in support for installation or configuration of rvrd; this section explains how to do it using the rvrd setup utilities.
Introduction
This section explains the basic setup that is required for having your administration domain span subnets. Setup needs to be performed:
Subject com.tibco.repo.>, using daemon and service (7500 by default). To filter out unneeded messages, you can also choose from this list. Replace repo_server_name with the name of your server and repo_instance with your server instance name.
 
      com.tibco.repo.repo_server_name.repo_instance.>
      com.tibco.repo.instance_discovery.request
      com.tibco.repo.server_discovery.request
      com.tibco.repo.serverHeartbeat.>
      com.tibco.repo.instance_mgmt.repo_server_name.request
If you use secondary servers in your domain, you must also perform setup for these subjects:
 
      _RVFT.>
      _RVCM.>
      _RVCMQ.>
Subject _HAWK.> (7474 by default) and subject com.tibco.pof.
This setup can be used at development time for all platforms. At runtime, you have two options:
On UNIX systems, you can prepare scripts that can start rvrd for both subjects automatically.
On Windows systems, only one Windows Service for rvrd is allowed. Because you would need one service for each subject, using a Windows system for runtime monitoring may therefore be challenging and is not recommended.
Setup Tasks
If you need to set up your domain to span subnets, the following steps are involved:
 
Install Administration Server
Install an administration server on one machine (you may later install secondary servers on additional machines for load balancing). Specify the domain name, user name, and password and note them for later use.
Decide the Services and Daemons the two Machines will use
For each machine, specify the services and daemons used for the two subjects on which the administration server sends and receives messages, for example (by default):
Figure 5 illustrates how rvrd communicates within and across the subnet: On host drink, rvrd will send out messages via rvrd to other applications in the subnet using udp 7500.
Figure 5 Setup of rvrd for Subject "com.tibco.repo.>"
 
Set up and start rvrd on the Administration Server Machine
On the administration server machine, TIBCO Rendezvous has been installed as part of the TIBCO Runtime Agent installation and you can set up rvrd without additional installation.
Setting up rvrd communication on the first machine consists of these steps:
1.
2.
On UNIX systems, kill the above processes.
3.
You cannot configure rvrd if rvd is running.
4.
You can start the services from the command-line, or using a batch file or script. Here’s an example of a Windows batch file:

 
@echo on
start c:\tibco\tibrv\bin\rvrd -store c:\tibco\drink7500.rvrd
           -listen 7500 -logfile c:\tibco\drink7500.out -http 7599
start c:\tibco\tibrv\bin\rvrd -store c:\tibco\drink7474.rvrd
           -listen 7474 -logfile c:\tibco\drink7474.out -http 7499

 
Configure the two rvrd daemons
To configure the two rvrd daemons, follow these steps:
1.
To access the TIBCO Rendezvous browser administration interface, point your browser to http://host_name:port. Host name can be a machine name or IP address, but sometimes a fully qualified name is required. Default port numbers are listed in TIBCO Rendezvous Administration. For example, http://ip-address:7580/.
2.
Figure 6 Enter Name of the Router
The router is listed, with a choice to configure local and neighbor interfaces.
Figure 7 Configure Local and Neighbor Interfaces
3.
Click the number under Local Network. In the screen that is displayed, type the local network name and the service, then click Add Local Network Interface.
Figure 8 Add Local Network Interface
4.
In the screen that appears, specify the subject to be used, either com.tibco.repo.> or _HAWK.>, then click Import and Export.
Figure 9 Specify the Subject to be Used
5.
Click Routers again in the left column and choose the number under Neighbor.
Figure 10 Router Configuration
 
6.
It is convenient to use the same port locally and remotely, but it is not necessary.
7.
Click Add Neighbor Interface. The information, including the IP address, is displayed.
8.
9.
Restart Administration Server and TIBCO Hawk Agent on First Machine
One easy way to do this on Windows platforms is to reboot the machine.
Set up Second Machine
The second machine is on a different subnet than the first. Setup of the second machine is similar to that of the first. Follow these steps:
1.
2.
3.
Second Machine Joins Domain
The final step is to invoke the TIBCO Domain Utility on the second machine and have that machine join the administration domain.
Troubleshooting
If your setup is not successful, that is, the components from the second machine do not show up on the domain inventory, consider these points:

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