Installation and Upgrade > Advanced Deployment Considerations > Installing and Configuring a Cluster Windchill Environment > Server Cluster Configuration Overview > Configuring the Windchill Environment for Clustering > Understanding Properties Used in Examples
  
Understanding Properties Used in Examples
The following table lists the properties used in the previous examples and describes their use:
Property
Description
wt.rmi.server.hostname=A
Each node in the cluster must act as if it were the cluster in its entirety. A request to an individual node in the cluster needs to generate the same response as every other node in the cluster. Set the local machine host lookup to resolve the common name to the current node. The following entry should be added in the server host file (UNIX host file is /etc/hosts; Windows host file is <WNNT>/system32/drivers/etc/hosts):
127.0.0.1 A
For clients to access these nodes as a single-server cluster, the RMI host name must be set to the commonly known name for the entire cluster, and in this case host A. This property should be set during installation.
wt.cache.master.slaveHosts=B, C, D
This property is required on all cluster nodes to allow the JMX management components to communicate from each node. The property also tells the Windchill cluster nodes that hosts in this property are trusted and allowed to access the slave node.
wt.cache.master.hostname=D
This property defines the host names that are allowed to become a cache master. When this property is not defined, any host in the cluster can become a cache master. When set, this property must be set on all cluster nodes.