Red Hat Directory Server 8.0 Administrator's Guide

nsds5replicatype: 2
nsds5ReplicaBindDN: cn=replication manager,cn=config
nsds5flags: 0
The replica entry attributes are described in Table 8.2, “Replica Attributes”. These attributes are
described in more detail in the Directory Server Configuration, Command, and File Reference.
7.3. Configuring Hubs from the Command Line
Hubs are intermediate read-only replicas which receive updates from suppliers and pass them
on to other consumers. These are part of the cascading replication scenario, described in
Section 2.3, “Cascading Replication”.Creating the hub has two steps: first, creating the
changelog database since the hub keeps a record of changes sent by the supplier, and second,
configuring the hub replica.
1. On the hub server, such as hub1.example.com, use ldapmodify to create the changelog
1
entry.
ldapmodify -v -h hub1.example.com -p 389 -D "cn=directory manager" -w
password
dn: cn=changelog5,cn=config
changetype: add
objectclass: top
objectclass: extensibleObject
cn: changelog5
nsslapd-changelogdir: /var/lib/dirsrv/slapd-instance_name/changelogdb
There is one important attribute with the changelog, nsslapd-changelogdir, which sets the
directory where the changelog is kept.
The changelog entry attributes are described in Table 8.1, “Changelog Attributes”. These
attributes are described in more detail in the Directory Server Configuration, Command, and
File Reference.
2. On the hub host, create the replica entry. This ldapmodify command creates a new hub
replica on the hub1.example.com host for the dc=example,dc=com subtree.
ldapmodify -v -h hub1.example.com -p 389 -D "cn=directory manager" -w
password
dn: cn=replica,cn="dc=example,dc=com",cn=mapping tree,cn=config
changetype: add
objectclass: top
objectclass: nsds5replica
objectclass: extensibleObject
cn: replica
nsds5replicaroot: dc=example,dc=com
nsds5replicatype: 2
Chapter 8. Managing Replication
316