Using Web Administration

Edit online

You can change the replica to a forwarding server using Web Administration Tool. Use the instructions provided here to perform the same.

Procedure

  1. Start all the servers.
  2. If you have not already done so, use the Web Administration Tool to log on to the master server (server1).
  3. Expand the Replication management category in the navigation area and click Manage topology.
  4. Select the subtree that you want to replicate and click Show topology.
  5. Click the box 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:
    • 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.

    • Leave the Enable SSL check box unchecked.
    • 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.
    • Enter a description of the replica server.
    • Specify the credentials that the replica uses to communicate with the master.
    1. Click Select.
    2. Click the radio button next to cn=replication,cn=IBMpolicies.
      Note: The mycreds credentials need to be created under cn=replication,cn=ibmpolicies on the forwarder, unless cn=ibmpolicies is replicated.
    3. Click Show credentials.
    4. Expand the list of credentials and select mycreds.
    5. Click OK.

      See Adding credentials for additional information on agreement credentials.

  8. Click the Additional tab.
    1. Keep the Specify a replication schedule or enter DN (optional) set to None. This sets the default as immediate replication.
    2. Do not deselect any capabilities.
    3. Keep the Replication method set to Single threaded.
    4. Click to select the Add credential information on consumer check box.
    5. Enter the administrator's DN for the consumer (replica) 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.
    6. Enter the administrator's password for the consumer (replica) server. For example secret.
    7. Click OK to create the replica. A message is displayed noting that additional actions must be taken, including restarting the replica server. Take the appropriate actions.
    8. Click OK.
  9. Copy data from server1 to the new replica server3. See Copying data to the replica for information about how to do that.
    Note: The topology changes are replicated to server2 by the master server1.
  10. Add the supplier agreement to server3 that makes server2 a supplier to server3 and server3 a consumer to server2. See Adding the supplier information to a replica for information about how to do this.
    Note: This step needs to be performed only if you did not select the Add credential information on consumer check box, or supplier information failed to be added to the consumer configuration file.

Results

The server roles are represented by icons in the Web Administration Tool. Your topology in now:
  • server1 (master)
    • server2 (forwarder)
      • server3 (replica)