HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

• When a replica is configured as a consumer or hub (a replica that receives updates from
another server), this entry must be specified as the one authorized to perform replication
updates.
• The replication agreement is created on the supplier server, the DN of this entry must be
specified in the replication agreement.
• The supplier bind DN entry must not be part of the replicated database for security reasons.
• This entry, with its special user profile, bypasses all access control rules defined on the consumer
server for the database involved in that replication agreement.
NOTE:
In the Directory Server Console, this replication manager entry is referred to as the supplier bind
DN, which may be misleading because the entry does not actually exist on the supplier server. It
is called the supplier bind DN because it is the entry that the supplier uses to bind to the consumer.
This entry actually exists, then, on the consumer.
For more information on creating the replication manager entry, see “Creating the supplier bind
DN entry” (page 324).
8.1.6 Replication agreement
Directory Servers use replication agreements to define their replication configuration. A replication
agreement describes replication between one supplier and one consumer only. The agreement is
configured on the supplier server and must specify all required replication information:
• The database to be replicated.
• The consumer server to which the data is pushed.
• The days and times during which replication can occur.
• The DN and credentials that the supplier server must use to bind (the replication manager
entry or supplier bind DN).
• How the connection is secured (SSL, client authentication).
• Any attributes that will not be replicated (fractional replication).
8.1.7 Replicating attributes with fractional replication
Fractional replication sets a specific subset of attributes that will not be transmitted from a supplier
to the consumer. Administrators can therefore replicate a database without replicating all the
information that it contains or all the information in every entry.
Fractional replication is enabled and configured per replication agreement. Excluding attributes
from replication is applied equally to all entries within the replication agreement's scope.
As far as the consumer server is concerned, the excluded attributes always have no value. Therefore,
a client performing a search against the consumer server will never see the excluded attributes.
Similarly, should it perform a search that specifies those attributes in its filter, no entries will match.
8.1.8 Compatibility with earlier versions of directory server
The replication mechanism in Directory Server 8.0 is different from the mechanism used in 4.x of
Directory Server. Compatibility is provided through two Directory Server plug-ins:
• Legacy Replication Plug-in
The Legacy Replication Plug-in makes a Directory Server 8.0 instance behave as a 4.x Directory
Server in a consumer role. For information on how to implement legacy replication using this
plug-in, see“Replication with earlier releases” (page 380).
• Retro Changelog Plug-in
8.1 Replication overview 319