Multiple clusters of Content Administration servers can deploy to a single target site. In order to implement this deployment topology, each cluster must have a unique identifier, which enables target site deployment agents to differentiate the deploying clusters. To establish a cluster’s identity, you configure each of its servers as follows:
Other requirements that are specific to Repository Assets and File Assets are discussed later in this section.
Set the cluster name
You can set the server’s cluster name in two ways:
In
/atg/dynamo/service/ClusterName, set theclusterNameproperty. Each Content Administration cluster name must be unique; within a cluster, all servers must set theirclusterNameproperty to the same value.Save the cluster name in the Content Administration database by setting two properties in
/atg/dynamo/service/ClusterName: setclusterNameas described above, and setuseClusterTabletotrue. On initial application startup, the server saves theclusterNamesetting to the database. When starting up later, the server checks the database name and compares it to theclusterName; ifclusterNameis empty, it uses the stored database value. If it finds a mismatch, it uses the property setting and writes this back to the database.By setting
useClusterTabletotrueon all cluster servers, you can set the cluster name on just one server, in order to propagate it to the others via the database.
Define the cluster hosts
Each server must be configured with contact data about the other servers in the cluster. For each server in a cluster, configure these properties in /atg/epub/Configuration:
remoteHosts: In a comma-delimited list, specify the host names of other servers in this server’s cluster.remoteRMIPorts: In a comma-delimited list, specify the RMI port settings that are configured for the hosts specified inremoteHosts. List the ports in the same order as the corresponding hosts.remotePorts: Set this property only if you use theFileSynchronizationDeployServerto synchronize distributed file system assets (see Manage Distributed File Assets).In a comma-delimited list, specify the file synchronization ports that are configured for the other servers in their
FileSynchronizationDeployServercomponents. List the ports in the same order as the corresponding hosts inremoteHosts.
For example:
remoteHosts=\ jupiter.acme-widgets.com,\ saturn.acme-widgets.com,\ uranus.acme-widgets.com remoteRMIPorts=\ 8860,\ 8860,\ 8860
