Creating and Maintaining Database Links
Then specify the configuration information for the database link, DBLink1, on
Server 1, as follows:
dn: cn=DBLink1,cn=chaining database,cn=plugins,cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsBackendInstance
nsslapd-suffix: 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="c=africa,ou=people,dc=example,dc=com",cn=mapping
tree,cn=config
objectclass=nsMappingTree
nsslapd-state=backend
nsslapd-backend=DBLink1
nsslapd-parent-suffix: c=africa,ou=people,dc=example,dc=com
cn: 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
attribute to check local ACIs, as this is only required on the database link,
DBLink2, on Server 2.
Since you want to implement loop detection, you need to specify the OID of the
loop detection control in the
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
loop detection control OID
check beforehand whether it already exists. If it does exist, you do not need to
perform this configuration step.
138
Red Hat Directory Server Administrator's Guide • May 2005
nsTransmittedControl
1.3.6.1.4.1.1466.29539.12
nsTransmittedControl
attribute is usually configured by default with the
nsCheckLocalACI
attribute stored in
entry on Server 1.
value, it is wise to
Need help?
Do you have a question about the DIRECTORY SERVER 7.1 - ADMINISTRATOR and is the answer not in the manual?
Questions and answers