Creating a replica server

 

Use this information to create a replica server.

The server must be running to perform this task.

Expand the Replication management category in the navigation area and click Manage topology.

1. Select the subtree that you want to replicate and click Show topology.

2. Click the arrow next to the Replication topology selection to expand the list of supplier servers.

3. Select the supplier server and click Add replica.

4. On the Server tab of the Add replica window:

   1. Enter the host name and port number for the replica you are creating. The default port is 389 for non-SSL and 636 for SSL. These are required fields.

   2. Select whether to enable SSL communications.

   3. Enter the replica name or leave this field blank to use the host name.

   4. Enter the replica ID. If the server on which you are creating the replica is running, click Get replica ID to automatically prefill this field. This is a required field, if the server you are adding is going to be a peer or forwarding server. IBM recommends that all servers be at the same release.

   5. Enter a description of the replica server.

5. On the Additional tab, specify the credentials that the replica uses to communicate with the master:

   The Web administration tool allows you to define credentials in these places:

   • cn=replication,cn=localhost, which keeps the credentials only on the server that uses them

   • Within the replicated subtree, in which case the credentials are replicated with the rest of the subtree. Credentials placed in the replicated subtree are created beneath the ibm-replicagroup=default entry for that subtree.

     Placing credentials in cn=replication,cn=localhost is considered more secure.

   1. Click Select.

   2. Select the location for the credentials you want to use. Preferably this is cn=replication,cn=localhost.

   3. Click Show credentials.

   4. Expand the list of credentials and select the one you want to use.

   5. Click OK.

   See Creating replication credentials for additional information on agreement credentials.

6. On the Additional tab, specify a replication schedule from the drop-down list or click Add to create one. See Creating replication schedules.

7. From the list of supplier capabilities, you can deselect any capabilities that you do not want replicated to the consumer.

   If your network has a mix of servers at different releases, capabilities are available on later releases that are not available on earlier releases. Some capabilities, like filter ACLs and password policy, make use of operational attributes that are replicated with other changes. In most cases, if these functions are used, you want all servers to support them. If all of the servers do not support the capability, you do not want to use it. For example, you would not want different ACLs in effect on each server. However, there might be cases where you might want to use a capability on the servers that support it, and not have changes related to the capability replicated to servers that do not support the capability. In such cases, you can use the capabilities list to mark certain capabilities to not be replicated.

8. Click OK to create the replica.

9. A message is displayed noting that additional actions must be taken. Click OK.

   If you are adding more servers as additional replicas or are creating a complex topolopogy, do not proceed with Coping data to the replica or Adding supplier information to the new replica until you have finished defining the topology on the master server. If you create the masterfile.ldif after you have completed the topology, it contains the directory entries of the master server and a complete copy of the topology agreements. When you load this file on each of the servers, each server then has the same information.

 

Parent topic:

Replication tasks