Duffbert's Random Musings

Document Number:  1089707

Problem
What are directory and database links, and how should they be used in a Domino environment?

Content
Directory and database links are simple text files with a .DIR or .NSF file extension located in the Notes data directory.  You can create these files using a simple text editor or through the Server Administration panel (see the Domino Administrator's Guide for details).  A link file contains a full path that points to another sub-directory or a specific database.  When the Notes client browses for available directories and databases, these link files appear as regular directories or databases.

Selecting a directory link file displays the contents of the directory specified in the file, and selecting a database link file opens the database specified in the file (assuming you have proper access via the Access Control List - ACL ).  Each link file can specify only one directory or database; however, the link file can also include a list of groups or users that have access to the link.  If a link file only contains the redirection link, then anyone can access the link.  Once one person or group is added, however, anyone needing to use the link must be specifically included in the file.

NOTE:        While you can control user access with these files, this added functionality is NOT a substitute for proper ACL implementation.

The intended usage of link files is for organization purposes.  For example, if you add an additional hard disk drive to your Domino server, you can move a single database or entire sub-directory to this new drive and still have it appear in the Notes data directory.  If, however, you relocate a production database or sub-directory with link files, workspace icons that point to this database or database(s) within a relocated sub-directory no longer work.  Even with link files, you must manage database relocation as outlined in the Domino Database Manager's Guide.

If you plan to implement directory or database link files, keep the following restrictions in mind:

• Never make a directory link point to the root of any drive.
• Point to local drives only.
• Link files can contain only one directory or database.
• Do not use link files to redirect a mail-enabled database (for example, mail-in databases and mail files).
• Use the security feature of link files to augment security, and not as a replacement for proper ACL implementation.
• Do not nest directory and database link files.
• An agent that is scheduled in the original database will be queued separately for each link, and thus, run more than once.  Refer to the document titled "Database Links in 4.6x Cause Scheduled Agents to Be Queued Separately for Each Link" (#179418 ) for more information.