For each cluster server, complete the deployment procedures described in Setting Up Deployment.

For each cluster server, set its serverName and drpPort properties in /atg/dynamo/service/ServerName.properties to values that are unique within the cluster.

For example, you might set server jupiter as follows:

serverName=jupiter:8850
drpPort=8850

Then you can set server saturn as follows:

serverName=saturn:18850
drpPort=18850

Set up a ServerLockManager and ClientLockManagers for the asset management server cluster. A ClientLockManager must be set up on each ATG server in the cluster. For information about configuring a ServerLockManager and ClientLockManagers, refer to the SQL Repository Caching chapter in the ATG Repository Guide.

Note: Do not run any ATG Content Administration modules or DAF Deployment on a standalone ServerLockManager. Doing so causes deployment deadlocks.

In order to Configure a Cluster for Switch Deployment, set each server’s remoteHosts, remoteRMIPorts, and remotePorts properties appropriately.

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 in remoteHosts. List the ports in the same order as the corresponding hosts.

remotePorts: Set this property only if you use the FileSynchronizationDeployServer to 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 FileSynchronizationDeployServer components. List the ports in the same order as the corresponding hosts in remoteHosts.