Setting up a complex topology with peer replication

Edit online

You can set up a complex topology with peer replication using the information provided here.

Initially, the ibm-replicagroup object created by this process inherits the ACL of the root entry for the replicated subtree. These ACLs might be inappropriate for controlling access to the replication information in the directory.

For the Add subtree operation to be successful, the entry DN that you are adding must have correct ACLs, if it is not a suffix in the server.
For Non-filtered ACLs :
ownersource : <the entry DN> 
ownerpropagate : TRUE
aclsource : <the entry DN> 
aclpropagate: TRUE
Filtered ACLs :
ownersource : <the entry DN> 
ownerpropagate : TRUE
ibm-filteraclinherit : FALSE
ibm-filteraclentry : <any value>

Use the Edit ACLs function of the Web Administration Tool to set ACLs for the replication information associated with the newly created replicated subtree (see Editing access control lists for the subtree).

Using the forwarding topology created in Changing the replica to a forwarding server, you are going to create a peer-forwarder-replica topology consisting of two peer-master servers, two forwarding servers, and four replicas. To create this topology, you must:
  1. Create two additional replica servers for the master server. See Adding a replica server.
  2. Create two replicas under each of the two newly created replica servers.
  3. Add a new peer master server. See Adding a peer-master or gateway server.
    Note: The server that you want to promote to a master must be a leaf replica with no subordinate replicas.
  4. Copy the data from the master to the new master and replicas. See Copying data to the replica.
  5. Start replication. See Managing queues.