Create a new replica server

If you have set up a replication topology (see Create a master server (replicated subtree)) with a master (server1) and a replica (server2), you can change the role of server2 to that of a forwarding server. To do this you need to create a new replica (server3) under server2.

1. Connect Web Administration to the master (server1)
2. Expand the Replication management category in the navigation area and click Manage topology.
3. Select the subtree that you want to replicate and click Show topology.
4. Click the arrow next to the Replication topology selection to expand the list of supplier servers.
5. Click the arrow next to the server1 selection to expand the list of servers.
6. Select server2 and click Add replica.

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

   • Enter the host name and port number for the replica (server3) you are creating. The default port is 389 for non-SSL and 636 for SSL. These are required fields.
   • 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. This is a required field, if the server you are adding is going to be a peer or forwarding server. It is recommended that all servers be at the same release.
   • Enter a description of the replica server.

   On the Additional tab:

   1. Specify the credentials that the replica uses to communicate with the master.
      Note:
      The Web administration tool allows you to define credentials in two 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.

      Placing credentials in cn=replication,cn=localhost is considered more secure. Credentials placed in the replicated subtree are created beneath the ibm-replicagroup=default entry for that subtree.
      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 Create credentials for additional information on agreement credentials.
   2. Specify a replication schedule from the drop-down list or click Add to create one. See Create replication schedules.
   3. 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.

   4. Click OK to create the replica.
8. Copy data from server2 to the new replica server3. See Copy data to the replica for information on how to do that.
9. Add the supplier agreement to server3 that makes server2 a supplier to server 3 and server 3 a consumer to server2. See Add the supplier information to the replica for information on how to do this.

The server roles are represented by icons in the Web administration tool. Your topology is now:

• server1 (master)
  • server2 (forwarder)
    • server3 (replica)