Adding a replica server

Edit online

You can learn to add a replica server using information provided here.

About this task

Note: The server must be running to perform this task.

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

Procedure

  1. Select the subtree that you want to replicate and click Show topology.
  2. Click the box next to the existing servers to expand the list of supplier servers.
  3. Select the supplier server and click Add replica.

Results

On the Server tab of the Add replica window:

  • From the Server hostname:port drop-down list, select an LDAP server for the replica server. If you want to provide another server as replica server, which is not registered on the console server, select Use entry from below item from the Server hostname:port drop-down list and then enter the host name and port number for the replica server in the field in the hostname:port format. The default port is 389 for non-SSL and 636 for SSL.
  • Select whether to enable SSL communications.
  • Enter the replica name or leave this field blank to use the host name.
  • 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.
  • Enter a description of the replica server.
  • You must specify the credentials that the replica uses to communicate with the master. Click Select.Note: The Web Administration Tool allows you to define credentials in the following places:
    • cn=replication,cn=localhost, which keeps the credentials only on the server that uses them. Placing credentials in cn=replication,cn=localhost is considered more secure.
    • cn=replication,cn=IBMpolicies, which is available even when the server under which you are trying to add a replica is not the same server that you are connected to with the Web Administration Tool. Credentials placed under this location are replicate to the servers. The location cn=replication,cn=IBMpolicies is only available, if the IBMpolicies support OID, 1.3.18.0.2.32.18, is present under the ibm-supportedcapabilities of the root DSE.
    • 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.
    1. Select the location for the credentials you want to use. Preferably this is cn=replication,cn=localhost.
    2. If you have already created a set of credentials, click Show credentials.
    3. Expand the list of credentials and select the one you want to use.
    4. Click OK.
    5. If you do not have preexisting credentials, click Add to create the credentials. See Adding credentials for additional information on agreement credentials.

On the Additional tab:

  1. Specify a replication schedule from the drop-down list or click Add to create one. See Creating replication schedules
  2. 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 (Filtered ACLs) and password policy (Password policy settings), make use of operational attributes that are replicated with other changes.In most cases, if these features 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.
  3. Select the either Single threaded or Multi-threaded for the method of replication. If you specify Multi-threaded, you must also specify the number (between 2 and 32) of connections to use for replication. The default number of connections is 2.
  4. Check the Add credential information on consumer check box, if you want to enable dynamic updates of the supplier credentials. This selection automatically updates the supplier information in the configuration file of the server you are creating. This enables the topology information to be replicated to the server.
    • Type the Administration DN for this, the consumer, server. For example cn=root.Note: If the administrator DN which was created during the server configuration process was cn=root, then enter the full administrator DN. Do not just use root.
    • Type the Administration password for this, the consumer, server. For example secret.
  5. Click OK to create the replica.
  6. A message is displayed noting that additional actions must be taken. Click OK.
Note:
  1. If you are adding more servers as additional replicas or are creating a complex topology, do not proceed with Copying data to the replica or Adding the supplier information to a 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.
  2. If an external credential object is selected while you are adding credentials on consumers during an Add replica operation using the Web Administration Tool, see the information in the note.