Contents Dochome
Sun Java(TM) System Directory Server Online Help

> # Replication Tab of Data Configuration

> This tab contains global settings for the replication mechanism.

> Note that some of these settings may also be initialized through the replication wizard. After using the wizard to create a replication agreement, the values you provided will appear on this tab, where you may modify them. Once these fields are initialized, either through the wizard or directly on this tab, the replication wizard will no longer prompt you to modify them.

> ## Replication Manager

> Directory Server has a default replication manager entry that you may specify in replication agreements. Suppliers use the replication manager entry to bind to a consumer server when sending replication updates. Its DN is cn=Replication Manager,cn=replication,cn=config.

> Password and Confirm Password. Type a password for the default replication manager in both fields. This is the password that you will use in replication agreements in which this server is the consumer.

> ## Replication Change Log

> The change log stores modifications made on a supplier server so that it can replicate them to its consumers. There is only a single change log per supplier server, regardless of how many suffixes are replicated.

> Enable change log. Select this checkbox to activate the change log. Normally, the change log will be enabled after configuring a suffix for replication.

> Caution | Unchecking the Enable change log checkbox will delete the change log file when you click the Save button. You will then need to reinitialize all consumer replicas of this server.

> Data changes will be stored in the following disk location. Enter the full path of a directory on the server host machine, or click Browse to select a location. This directory should be located on a disk with enough space for your intended change log size. The default change log directory is:

> Solaris 9 platform | /var/ds5/slapd-serverID/changelogdb
> Other platforms | /usr/sunone/servers/slapd-serverID/changelogdb

> Caution | Renaming an existing change log while replication is active will delete the change log file when you click the Save button. You will then need to reinitialize all consumer replicas of this server.

> Max change log records. Deselect the unlimited checkbox and enter the maximum number of modification records you wish to store in the change log. When the maximum number is reached, the oldest records will be deleted automatically. Limiting the number of records will save disk space if your replica receives many large modifications.

> Leaving the unlimited checkbox selected means the change log will grow indefinitely if you do not set a max change log age.

> Max change log age. Deselect the unlimited checkbox and enter the number and units of the maximum age for change log records. Records older than the maximum age are deleted automatically. The max age parameter is the recommended way to limit the size of the change log.

> Leaving the unlimited checkbox selected means the change log will grow indefinitely if you do not set the max change log records field.

> ## Version 4.x Compatibility

> To help migrate data from legacy servers, Sun Java™ System Directory Server 5.2 may be configured as a consumer of legacy Directory Server 4.x suppliers.

> Allow replicas to be 4.x compatible. Select this checkbox to enable the legacy replication plug-in that will receive updates from 4.x suppliers.

> Bind DN. Give the DN of a replication manager entry that you will specify in the 4.x supplier server to access this replica.

> Password and Confirm Password. Type the password for the bind DN in both fields. The bind DN passwords are not necessary if the legacy 4.x supplier will connect over SSL using certificates for authentication.

> ## Fractional Replication

> Fractional replication is the mechanism for replicating only certain attributes in a replicated suffix.

> Manage Replicated Attribute Sets. This button invokes the attribute set manager that allows you to define and name sets of attributes. You can configure fractional replication by editing a replication agreement to use one of these sets. All consumers of that replica will then only contain the attributes defined in the set.

> ## See Also

> Chapter 8, "Managing Replication," in the Sun Java System Directory Server Administration Guide.

> Contents Dochome

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.