Creating and Maintaining Database LinksChapter 3 Configuring Directory Databases 115Providing an LDAP URLOn the server containing your database link, you have to identify the remote serverthat the database link connects with using an LDAP URL. Unlike the standardLDAP URL format, the URL of the remote server does not specify a suffix. It takesthe following form:ldap://hostname:portnumberYou specify the URL of the remote server using the nsFarmServerURL attribute inthe cn=database_link_name,cn=chaining database,cn=plugins,cn=config entryof the configuration file. For example, the nsFarmServerURL might appear asfollows:nsFarmServerURL: ldap://example.com:389/Do not forget to use the trailing slash (/) at the end of the URL.If you want the database link to connect to the remote server using LDAP over SSL,the LDAP URL of the remote server takes the following form:ldaps://hostname:portnumberFor more information about chaining and SSL, refer to “Chaining Using SSL,” onpage 120.Providing a List of Failover ServersYou can include additional LDAP URLs for servers to use in the case of failure. Todo so, add alternate servers to the nsFarmServerURL attribute, separated by spaces.For example, you might enter the following:nsFarmServerURL: ldap://example.com us.example.com:389africa.example.com:1000/In this sample LDAP URL, the database link first contacts the server example.comon the standard port to service an operation. If it does not respond, the databaselink then contacts the server us.example.com on port 389. If this server fails, itthen contacts africa.example.com on port 1000.Summary of Database Link Configuration AttributesThe following table lists the attributes available for configuring a database link.Some of these attributes were discussed in the earlier sections.Attributes marked with an asterisk (*) can be both global or instance attributes. Allinstance attributes are defined in the cn=database_link_name,cn=chainingdatabase,cn=plugins,cn=config entry.
