The following is a sample replication configuration container entry:

dn: cn=replication configuration
orclaci: access to entry by * (browse)
orclaci: access to attr=(*) by * (search,read)
orclnormdn: cn=replication configuration
cn: replication configuration
description: Replication agreement Container object
objectclass: top
objectclass: orclcontainerOC

The following is a sample replication naming context container entry:

dn: cn=replication namecontext,orclagreementid=000002, 
 orclreplicaid=myhost1_repl1,cn=replication configuration
objectclass: top
objectclass: orclcontainerOC
cn: replication namecontext

The examples of replication objects in this section rely on the replication environment shown in Figure 43-1.

In Figure 43-1, nodes A, B, and C form a multimaster replication group. Node C replicates to a fourth node, D, which, in turn, fans out to Node E.

The replication agreements in this environment are as follows:

• Node A has one replication agreement representing its multimaster relationship with nodes B and C.

• Node B has two replication agreements, the first representing its multimaster relationship with nodes A and C, the second representing its relationship to node F. The replication agreement between B and F is two-way.

• Node C has two replication agreements, the first representing its multimaster relationship with nodes A and B, the second representing its relationship to node D. This is a one-way replication agreement in which C serves as the supplier and node D is the consumer.

• Node D has two replication agreements. Both of its replication agreements are one-way. One represents its relationship to the supplier node C, from which it consumes changes, the other represents its relationship to consumer node E for which it is the supplier.

• Node E has a one-way replication agreement with Node D. Node E is the consumer.

• Node F has two replication agreements, one representing its relationship to the node B, the other representing its relationship to node G.Both are two-way replication agreements.

• Node G has a one-way replication agreement with Node F. Node G is the consumer.

Figure 43-2 shows the replication objects in the DIT that pertain to node C in Figure 43-1 .

For node C, the entry cn=replication configuration at the root DSE contains these RDNs:

• orclagreementID=000001: The multimaster replication agreement in which node C participates with nodes A and B.

• orclReplicaID=UID_of_node_C: Unique identifier of node C that contains information about it.

• orclagreementID=000002: Unique identifier of the relationship between supplier node C and consumer node D. You know that, in this case, orclagreementID=000002 is the replication agreement of the supplier node C because node C is its parent.

  This entry contains the attribute orclreplicaDN. Its value is the replica entry DN of consumer node D, with which node C has the replication agreement.

• cn=replication DN: The bind DN that the directory replication server on node C uses to bind to the directory server.

• cn=replication namecontext: Container of information about naming contexts that are included in replication.

• cn=includednamingcontext000001 and cn=namingcontext002: The actual objects that are included in or excluded from replication. In the naming context included for replication, you can specify one or more subtrees to be excluded from replication. In that same included naming context, you can specify particular attributes to be excluded from replication.

Figure 43-3 shows the replication agreement entry in the DIT that pertains to node D in Figure 43-1.

For node D, the entry cn=replication configuration at the root DSE contains these RDNs:

• orclReplicaID=UID_of_node_D: Unique identifier of node D and contains information about it.

• orclagreementID=000003: Unique identifier of the relationship between supplier node D and consumer node E. You know that, in this case, orclagreementID=000003 is the replication agreement of the supplier node D because node D is its parent.

  This entry contains the attribute orclreplicaDN, the value of which is the DN of consumer node E with which node D has the replication agreement.

• cn=replication DN: Bind DN that the directory replication server on node D uses to bind to the directory server.

• cn=replication namecontext: Container of information about naming contexts that are included in replication.

• cn=namingcontext001 and cn=namingcontext002: Objects specifying naming contexts to be included in replication. In the naming context included in replication, you can specify one or more subtrees or particular attributes to be excluded from replication.