Apply the LDIF file by typing:

Managing Replication Configuration Attributes 40-5 Oracle Database Advanced Replication-Based Replication Agreements For Advanced Replication, the replication agreement on each node lists all of the nodes in the group. It is identical on each node except for local options such as partitioned naming contexts on the local directory server. The entry for this kind of replication agreement resides immediately below the cn=replication configuration container entry. For example, the DN of such an agreement can look like this: orclagreementID=000001,cn=replication configuration. LDAP Replication Agreements For LDAP-based replication, there are separate replication agreements for each supplier-consumer relationship. For one-way replication, there is a single, one-way replication agreement. The entry for an LDAP-based replication agreement resides immediately below the replica subentry of the node that serves as the supplier. Thus, the DN of the replication agreement as found on a supplier node is: orclagreementID=unique_identifier_of_the_replication_agreement, orclReplicaID=unique_identifier_of_supplier_node, cn=replication configuration Similarly, the DN of the replication agreement as found on a consumer node is: orclagreementID=unique_identifier_of_the_replication_agreeement, orclReplicaID=unique_identifier_of_supplier_node, cn=replication configuration In a fan-out replication agreement, you can tell which node the agreement entry is associated with by looking at its parent. For example, look at the following replication agreement entry. orclagreementID=000002,orclReplicaID=node_A,cn=replication configuration In this example, you can determine that the replication agreement represented by orclagreementID=000002 is associated with node A. This is because the parent of orclagreementID=000002 is orclReplicaID=node_A. Two-Way LDAP Replication Agreements For two-way replication, there can be either a single, two-way replication agreement or two one-way agreements for each supplier-consumer relationship. The following is a sample two-way replication agreement entry: dn: orclagreementid=000002, orclreplicaid=stadd58_repl, cn=replication configuration Notes: ■ The container entry cn=replication configuration is replicated on all nodes, but may not be identical on all nodes. ■ The orclreplicadn attribute of an LDAP-based replication agreement specifies the associated consumer node. ■ The agreementtype indicates the replication agreement type. See Table 40–2, Attributes of the Replication Agreement Entry for values of orclagreementtype. 40-6 Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory orclagreementid: 000002 orclreplicationprotocol: ODS_LDAP_1.0 orclreplicadn: orclreplicaid=stadd57_repl,cn=replication configuration orclldapconnkeepalive: 1 orclagreementtype: 1 orclreplicationid: 000002 orcllastappliedchangenumber;transportstadd57stadd58: 106 orcllastappliedchangenumber;transportstadd58stadd57: 2421 orcllastappliedchangenumber;applystadd57stadd58: 106 orcllastappliedchangenumber;applystadd58stadd57: 2421 orclupdateschedule: 0 orclhiqschedule: 60 objectclass: orclReplAgreementEntry objectclass: top The Replication Naming Context Container Entry This entry contains all the LDAP naming context objects. This entry has the RDN cn=replication namecontext, and it is created below the orclagreementID entry during replication configuration. 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 Replication Naming Context Object Entry This entry contains all the LDAP naming context objects. These objects specify the replication filtering policy, that is, what to include in or exclude from replication to an LDAP-based partial replica. This entry is created below the naming context container entry during replication configuration. It is configurable. For example, in Figure 40–3 on page 40-12, the replication naming context object is: cn=includednamingcontext000001,cn=replication Note: The value of orclagreementtype is 1 because this is a two-way replication agreement. See Table 40–2, Attributes of the Replication Agreement Entry for values of orclagreementtype for other replication agreement types. See Also: Replication Schema Elements in Oracle Fusion Middleware Reference for Oracle Identity Management for descriptions of the attributes of the replication agreement entry Note: You cannot include naming contexts or exclude attributes in Oracle Database Advanced Replication-based agreements. Advanced Replication agreements use the base attribute orclexcludednamingcontexts described in Table 40–2 . Managing Replication Configuration Attributes 40-7 namecontext,orclagreementID=000003,orclReplicaID=UID_of_node_ D ,cn=replication configuration. Table 40–3 describes the attributes of the replication naming context entry. If you use the Replication Wizard in Oracle Enterprise Manager Fusion Middleware Control to set up replication, you set these on the Scope page. The following is a sample replication naming context object entry: dn:cn=namectx001, cn=replication namecontext, orclagreementid=unique_identifier_of_the_replication_agreement, orclreplicaid=replica_id_of_node_A, cn=replication configuration orclincludednamingcontexts: cn=mycompany orclexcludednamingcontexts; replica_id_of_node_A replica_id_of_node_B : c=us,cn=mycompany orclexcludedattributes; replica_id_of_node_B replica_id_of_node_A : userPassword Table 40–3 Attributes of the Replication Naming Context Entry Attribute Description orclincludednamingc ontexts The root of the naming context to be replicated. If orclincludednamingcontexts is set to , all the naming contexts are replicated. This attribute has subtypes that specify the replication direction in which the naming context should be included. The format is: orclincludednamingcontexts ; supplier_ replicaID consumer_replicaiD: DN This is a single valued attribute. For each naming context object, you can specify only one unique subtree in each direction. In partial replication, except for subtrees listed in the orclexcluednamingcontexts attribute, all subtrees in the specified included naming context are replicated. You can modify this attribute. orclexcludednamingc ontexts The root of a subtree, located within the included naming context, to be excluded from replication.This attribute has subtypes that specify the replication direction in which the naming context should be excluded. The format is: orclexcludednamingcontexts; supplier_ replicaID consumer_replicaiD : DN This is a multivalued attribute. From within the naming context specified in the orclincludednamingcontexts attribute, you can specify one or more subtrees to be excluded from the partial replication in each direction. You can modify this attribute. orclexcludedattribu tes An attribute, located within the included naming context, to be excluded from replication. Orclexcludedattributes has subtypes that specify the replication direction in which the specified attribute should be excluded. The format is: orclexcludedattributes; supplier_replicaIDconsumer_ replicaiD : attribute_name This is a multivalued attribute. You can modify this attribute 40-8 Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory The example specifies the following replication filtering: ■ The naming context cn=mycompany is included for replication in both directions for node A and node B. ■ The naming context c=us,cn=mycompany is excluded for replication from node A to node B only. ■ The userPassword attribute is excluded for replication from node B to node A The Replication Configuration Set The replication configuration set has the DN: cn=configset0,cn=osdrepld,cn=subconfigsubentry Table 40–4 lists and describes the attributes of the replication configuration set, which has the following DN: cn=configset0,cn=osdrepld,cn=subconfigsubentry You must restart the replication server in order for any attribute changes under this DN to take effect, except for the attribute orcldebuglevel. Under Update Mechanism, EM indicates that you can manage this attribute with Oracle Enterprise Manager Fusion Middleware Control. LDAP indicates that you can manage this attribute by using LDAP tools. See Also: ■ Examples of LDAP Replication Filtering on page 38-8 ■ Replication Schema Elements in Oracle Fusion Middleware Reference for Oracle Identity Management Table 40–4 Replication Configuration Set Attributes Attribute Description Update Mechanism Default Possible Values modifyTimestamp Time of entry creation or modification. Read-only modifiersName Name of person creating or modifying the entry Read-only orclChangeRetryCo unt Number of processing retry attempts for a change-entry before being moved to the human intervention queue. EM, LDAP 10 Greater than or equal to 1. orclThreadsPerSup plier;transport Number of worker threads spawned at each supplier for transporting change logs. EM, LDAP 1 1-100 orclThreadsPerSup plier;apply Number of worker threads spawned at each supplier for applying change logs. EM, LDAP 5 1-100 orclreplautotune Dynamically vary the number of threads assigned to transport and apply tasks based on load. If you set the server to auto tune, you must specify the number of maximum number of threads to be shared between these tasks. Restart server after changing. EM, LDAP 1 0: Off 1: On Managing Replication Configuration Attributes 40-9 Examples of Replication Configuration Objects in the Directory The examples of replication objects in this section rely on the replication environment shown in Figure 40–1 . orclreplmaxworker s Maximum number of worker threads. Required if orclreplautotune is set. EM, LDAP 20 1-100 orclsdumpflag Generate stack dump. Restart after changing. EM, LDAP 0: False 1: True orclmaxlogfilesiz e Maximum log file size MB EM, LDAP 1 MB or = 1 orclmaxlogfiles Maximum number of log files to keep in rotation EM, LDAP 100 or = 1 orclsizelimit Maximum number of entries to process per replication cycle EM, LDAP 1000 1-10000 orclconflresoluti on Automatically resolve replication conflicts EM, LDAP 1 0: False 1: True orclreplusesasl;d igest-md5 Use SASL for replication binds. EM, LDAP Attribute does not exist by default. auth, auth-int, auth-conf orclActivateRepli cation Specifies that replication be activated on the replication server designated by orclOidInstanceName and orclOidComponentName. EM, LDAP 0: False 1: True orclReplicationSt ate Activation state of the replication server Read-only, using EM, LDAP 0 or nonexistant: Not running False 1: Running orcldebuglevel Debug level of replication server EM, LDAP Values are additive: 0: No Debug Log 2097152: Replication Performance Log 4194304: Replication Debug Log 8388608: Function Call Trace 16777216: Heavy Trace Log orclOidComponentN ame Name of OID component where replication is or will be activated Read-only Set during replication setup String orclOidInstanceNa me Instance number of instance where replication is or will be activated Read-only Set during replication setup Integer orclReplAttrConfl ict Specifies whether timestamp or attribute version should be honored first during attribute level conflict resolution. EM, LDAP 0: Timestamp first. 1: Version number first Table 40–4 Cont. Replication Configuration Set Attributes Attribute Description Update Mechanism Default Possible Values 40-10 Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory Figure 40–1 Example: Multimaster Replication and Fan-Out Replication In Figure 40–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. A C B D F E Multimaster Replication G Fan-Out Replication Multimaster Replication-based Replica Partial Replica One-Way Replication Two-Way Replication Multimaster Replication