HP-UX Directory Server 8.1 administrator guide

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”.
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”.
• Retro Changelog Plug-in
The Retro Changelog Plug-in can be used for a Directory Server supplier to maintain a
4.x-style changelog. This is sometimes necessary for legacy applications that have a
dependency on the Directory Server 4.x changelog format because they read information
from the changelog. For more information on the Retro Changelog Plug-in, see “Using the
Retro changelog plug-in”.
8.1 Replication overview 321