Administration Guide
Overview Guide
Installation Guide
Previous Next Contents



Mapping the Synchronizer to the Cluster
For a cluster to communicate, the synchronizer in each server must know to which cluster the synchronizer belongs. This is done by mapping the ClusterName key of each synchronizer to the name of an actual cluster.

To map the synchronizer to a cluster, follow these steps.

  1. Stop the Netscape Application Server whose registry you will edit.
  2. Be aware that editing the server registry while the Netscape Application Server is running can cause serious problems. Also, some changes take effect only after the engine is recycled.

  3. Open the registry editor.
  4. The registry editor displays the keys and values that apply to the Netscape Application Serve. The appearance varies slightly between the UNIX and Windows NT systems.

  5. Open the registry folder. Notice that this path differs slightly from the previous path that was used to modify or create a cluster.
  6. The following figure displays a registry section on a UNIX system in which the Default cluster has already been renamed "SampleCluster:"

    The same information displays in regedit on a Windows NT system, but in two side-by-side windows.

    KIVA\\Enterprise\\2.0\\CCS0\\ClusterName

  7. Rename the key under ClusterName to the name of the cluster to which the synchronizer should connect.
  8. If this key has not been previously modified, then the name under ClusterName will be Default. For more information about the Default cluster, see "Modifying the Default Cluster for Fast Cluster Set Up."

  9. Close the registry editor when you are finished. The synchronizer should now be mapped to the cluster
 

© Copyright 1998 Netscape Communications Corporation