Netscape DIRECTORY SERVER 6.2 - ADMINISTRATOR Administrator's Manual page 131

Creating and Maintaining Database Links
Then specify the configuration information for the database link, DBLink1, on
server one as follows:
dn: cn=DBLink1,cn=chaining database,cn=plugins,cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsBackendInstance
nsslapd-suffix: l=Zanzibar,c=africa,ou=people,dc=example,dc=com
nsfarmserverurl: ldap://africa.example.com:389/
nsmultiplexorbinddn: cn=server1 proxy admin,cn=config
nsmultiplexorcredentials: secret
cn: DBLink1
nsCheckLocalACI:off
cn="l=Zanzibar,c=africa,ou=people,dc=example,dc=com",cn=mapping
tree,cn=config
objectclass=nsMappingTree
nsslapd-state=backend
nsslapd-backend=DBLink1
nsslapd-suffix: l=Zanzibar,c=africa,ou=people,dc=example,dc=com
cn: l=Zanzibar,c=africa,ou=people,dc=example,dc=com
The first section creates the entry associated with DBLink1. The second section
creates a new suffix, allowing the server to direct requests made to the database
link to the correct server. You do not need to configure the
nsCheckLocalACI
attribute to check local ACIs, as this is only required on the database link, DBLink2,
on server two.
Since you want to implement loop detection, you need to specify the OID of the
loop detection control in the attribute stored in
nsTransmittedControl
entry on server one.
cn=config,cn=chaining database,cn=plugins,cn=config
You specify the OID as follows:
dn: cn=config,cn=chaining database,cn=plugins,cn=config
changeType: modify
add: nsTransmittedControl
nsTransmittedControl: 1.3.6.1.4.1.1466.29539.12
As the attribute is usually configured by default with the
nsTransmittedControl
loop detection control OID value, it is wise to check
1.3.6.1.4.1.1466.29539.12
beforehand whether or not it already exists. If it does exist you do not need to
perform this configuration step.
Chapter 3 Configuring Directory Databases 131