Domain Nodes and Domain Composition
How do I get to this dialog box?
From the Administrative Console
- On Domain Composition tab, under Domain Nodes, select a node.
A Reflection X domain consists of one or more domain nodes (computers in the domain). Each domain must have one domain controller, which runs the domain controller service. Domains can also have additional domain nodes that are used to run sessions, which support session persistence. Domain nodes can also be installed on application hosts to enable compression from the host.
Shows nodes that have been configured for this domain. The node includes a port assignment if it is not the default value (22001).
Use the rxsconfig utility to add and remove the registered domain nodes displayed here. For details, see Set Up Domain Nodes and Remove a Domain Node. Although you can delete a node here, this will not remove its configuration on the domain node machine.
If the domain node icon shows a red slash, the node is unavailable. For troubleshooting, see Domain Node is Unavailable.
|Node||The DNS network name or IP address of the domain node|
|Friendly name||Set the domain node name. This name is displayed in the Domain Composition and Domain Status tabs. Specify a name that easily distinguishes this domain node from others.|
|Alternate addresses||To connect to a domain node through a firewall that is using Network Address Translation (NAT), you must specify the alternate public address that Reflection X should use for the connection.|
|Supply a comma delimited list of hosts and their associated ports. For example:|
|If the port is omitted, the port from the listening address is used|
|Relative capacity||Set the performance capacity of this node relative to others in the domain to fine tune load balancing. For example, if you have two domain nodes (computers) with roughly the same CPU and memory, but you want to use one of them for other tasks, you can set the relative capacity of that server to the Low end of the scale. When the Reflection X Domain Controller performs load balancing, it is less likely to assign sessions to that node.|
|Participate in domain||Configures the node to service new sessions. When cleared, the node is removed from the load balancing scheme. The Reflection X Domain Controller does not start new sessions or client connectors on the node. This allows you to prepare a node for shutdown (or reboot) without impacting running sessions.|
When your domain is supporting multiple sessions that are using session persistence, Reflection X may need to run more than one session on each domain node. Load balancing improves session performance by ensuring that the load is distributed among all of the nodes. The load balancing scheme you select here is used for the entire domain. To adjust load capacity for each domain node, use the Relative capacity slider.
|Round Robin||Balances load by starting sessions and connectors on a rotating basis.|
|Optimize CPU||Balances load by starting sessions on the basis of the best available CPU resources.|
|Optimize memory||Balances load by starting sessions on the basis of the best available memory resources.|