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 : Multiple Administration Domains in a Subnet

Multiple Administration Domains in a Subnet
You can have multiple administration domains in a single subnet (or even on a single machine). The primary servers may be used in conjunction with multiple administration domains, or standalone without domains.
Multiple Administration Domains discusses multiple TIBCO administration domains, each with its own primary server.
Multiple Servers Using Different Daemon and Service Properties discusses the same scenario for situations where the domain management and security component is not installed.
Multiple Administration Domains
You can have multiple TIBCO administration domains in the same subnet or on the same machine. Each administration domain must have its own administration server.
Each domain on a specific machine must have its own name.
In the next illustration, one server is using a domain D1 and another server is using a domain D2. Each server must be a primary server.
You can choose to use HTTP for communication between the server and associated project or application repository. However, when you deploy applications or view machine inventory or alert information, the server retrieves this information using TIBCO Hawk agent and it can only communicate with the server using TIBCO Rendezvous.
Figure 4 Multiple Domains in a Single Subnet
Multiple Servers Using Different Daemon and Service Properties
You can use the daemon port and service properties to set up multiple servers in a single subnet. The service port number defines the TIBCO Rendezvous service to be used for the subnet. The different service numbers assigned to different administration servers and their client applications can be used to partition subnets.
You can assign different service and daemon port numbers using the TIBCO Domain Utility.
Each client application must set the service and daemon to the port number of the administration server on the same subnet. The properties are set when a machine joins an administration domain and when an application is deployed.
On computers with more than one network interface, the network parameter instructs the Rendezvous daemon to use a particular network for all communications involving this transport. To communicate over more than one network, a program must create a separate transport object for each network. See the TIBCO Rendezvous Concepts guide for details.

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