Configuring Directory Server As A Consumer Of A Legacy Directory Server - Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual

Replication with Earlier Releases
• This version of Directory Server cannot be a supplier for other replicas.
The main advantage of being able to use this version of Directory Server as a
consumer of a legacy Directory Server is to ease the migration of a replicated
environment. For more information on the steps to follow to migrate a replicated
environment, refer to the Red Hat Directory Server Installation Guide.
Configuring Directory Server as a Consumer of a
Legacy Directory Server
If you intend to use your Directory Server as a consumer of an earlier release of
Directory Server, you must configure it as follows:
In the Directory Server Console, click the Configuration tab.
1.
For information on starting the Directory Server Console, "Using the
Directory Server Console," on page 34.
In the Configuration tab, select the Replication node, and click the Legacy
2.
Consumer Settings tab in the right pane.
Check the Enable Legacy Consumer checkbox.
3.
This activates the fields in the Authentication box.
Specify the Supplier DN that the legacy supplier server will use to bind.
4.
Optionally, you can specify a password. The password must contain at least 8
characters.
Click Save.
5.
You must now configure legacy consumer settings for each replica that will
receive updates from a legacy supplier.
In the navigation tree, expand the Replication node, and select a replica that
6.
will receive updates from the legacy supplier.
In the Replica Settings tab, select the Enable Replica and "Updatable by a 4.x
7.
Replica" checkboxes.
These options are the only ones required for replication to work. You can
optionally specify a Replica ID. It is not necessary to specify a Supplier DN
because the one you specified in Step 4 will be used.
Click Save.
8.
356 Red Hat Directory Server Administrator's Guide • May 2005