Replication Configuration Objects in the Directory

This section describes the objects in the directory that contain replication configuration information. It contains these topics:

• The Replication Configuration Container

• The Replica Subentry

• The Replication Agreement Entry

• The Replication Naming Context Container Entry

• Examples of Replication Configuration Objects in the Directory

The Replication Configuration Container

All replication information for a node resides in the container cn=replication configuration located at the root DSE. This entry resides on each node in a DRG.

The Replica Subentry

This subentry is created at installation under the replication configuration container. It contains attributes that identify and define the characteristics of the node it represents.

This subentry is associated with the object class orclReplicaSubentry. It contains the attribute orclreplicaID whose value specifies the name of the replica subentry. It is unique to each directory node, and matches that of the orclreplicaID attribute at the root DSE. For example, in Figure 24-9, a replica subentry is represented by orclReplicaID=UID_of_node_D,cn=replication configuration.

See Also: Table B-31 for descriptions of the attributes of the replica subentry.

The Replication Agreement Entry

This entry contains attributes that define the replication agreement between a consumer and a supplier. It resides under the replication configuration entry, and is associated with the orclReplAgreementEntry object class. The naming attribute of this entry is orclagreementID. For example, in Figure 24-9, a replication agreement entry is represented by orclagreementID=000003,orclReplicaID=UID_of_node_D,cn=replication configuration.

See Also: Table B-32 for descriptions of the attributes of the replication agreement entry

The Replication Naming Context Container Entry

This entry contains all the LDAP naming context objects. These objects specify what is to be either included in or excluded from replication to an LDAP-based partial replica.

This entry has the RDN cn=replication namecontext, and it is created below the orclagreementID entry at installation.

A replication naming context contains these objects:

• orclincludednamingcontexts--The root of the naming context to be replicated

• orclexcludednamingcontexts--Within the included naming context, the root of a subtree to be excluded from replication

• orclexcludedattributes--Within the included naming context, an attribute to be excluded from replication

  See Also: Table B-33 for descriptions of the attributes in the replication naming context container entry

Examples of Replication Configuration Objects in the Directory

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

Figure 24-7 Example: Multimaster Replication and Fan-Out Replication

Text description of the illustration oidag094.gif

In Figure 24-7, 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 one replication agreement representing its multimaster relationship with nodes A and C.

• 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 in which it serves as the supplier and node D is the consumer.

• Node D has two replication agreements, one representing its relationship to the supplier node C, from which it consumes changes, the other representing its relationship to consumer node E for which it is the supplier.

Figure 24-8 shows the replication objects in the DIT that pertain to node C in Figure 24-7.

Figure 24-8 Example: Replication Configuration Entries for Node C

Text description of the illustration oidag090.gif

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, the value of which is the DN of consumer node D with which node C has the replication agreement.

• cn=replicationDN: 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=namingcontext001 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 24-9 shows the replication agreement entry in the DIT that pertains to node D in Figure 24-7.

Figure 24-9 Example: Replication Configuration Entries for Node D

Text description of the illustration oidag091.gif

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=replicationDN: 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.