Step 1: Verify that each Domino Directory has a defined domain

Each IBM® Lotus® Domino™ Directory aggregated in a directory catalog should have a domain defined in its Directory Profile. The Dircat task appends the domain name to the names of groups in the directory catalog, to distinguish between identically named groups from different directories.

Do the following for each Domino Directory you will aggregate into the directory catalog:

1. Open a Domino Directory.

2. Choose Actions - Edit Directory Profile.

3. Make sure the field "Domain defined by this Domino Directory" contains a valid domain name. This field is usually filled in automatically.

4. Click Save & Close.

Step 2: Create the condensed Directory Catalog database

1. Choose File - Application - New.

2. Next to Server, select the Dircat server you picked to aggregate the directory catalog.

3. Next to Title, enter a title for the directory catalog, for example Condensed Directory Catalog.

4. Next to Filename, enter a file name for the catalog, for example CDC.NSF.

5. Select "Create full text index for searching."

6. Click "Show advanced templates."

7. Below "Template server," select a server that stores the Directory Catalog template, and then click OK.

8. Select the Directory Catalog template (DIRCAT5.NTF). Do not select the Catalog (V6) template (CATALOG.NTF).

9. Click OK.

Note Keep the - Default - entry in the database access control list (ACL) set to Reader.

Note You only need one configuration document for each directory catalog you create. Therefore, when you open the Configuration view, the configuration document is displayed.

1. In the database you created, open the Configuration view.

2. Complete the following fields in the Directory Catalog Configuration document:

Note The "Directories to include" field is the only field you must complete. In many situations you can accept the default values in the other fields. However, read the complete descriptions of the fields before you run the Dircat task to build the directory catalog.

Fields in Basics tab	Description
Directories to include	Specifies which Domino Directories the Dircat task aggregates, and the order in which it processes the directories. For more information, see the earlier topic "Specifying the Domino Directories for the Dircat task to aggregate."
Additional fields to include	Specifies which fields from Domino Directories to aggregate. For more information, see the earlier topic "Choosing which fields to aggregate in a directory catalog."
Sort by	Specifies how to sort entries in the directory catalog. For more information, see the earlier topic "Deciding how to sort entries in a condensed Directory Catalog."
Use Soundex	Specifies whether to support Soundex lookups. For more information, see the earlier topic "Supporting Soundex searches of a condensed Directory Catalog."
Remove duplicate users	Specifies whether to aggregate multiple user entries with the same name. For more information, see the earlier topic "Removing duplicate user entries from a directory catalog."
Group types	Specifies which types of groups to aggregate. For more information, see the earlier topic "Choosing the types of groups to aggregate in a directory catalog."
Include Mail-in Databases	Specifies whether to aggregate Mail-In Database documents. Default is Yes. Consider setting to No if the directory catalog is used only on clients, since IBM® Lotus® Notes® users don't typically send mail to Mail-In Databases.
Restrict aggregation to this server	(Recommended) Specifies the one Dircat server that can aggregate this directory catalog. For more information, see the earlier topic "Allowing only one server to aggregate a directory catalog."
Send Directory Catalog reports to:	(Optional) Specifies the names of people to receive Directory Catalog status reports. For more information, see the later topic "Mailing Directory Catalog reports."

Fields in Advanced tab	Description
Version	Read only field that can increment after a Domino upgrade.
Selection formula	(Optional) Specifies a selection formula to control which documents are aggregated. For more information, see the earlier topic "Using a selection formula in a directory catalog configuration document."
Total number of people/group/mail-in databases and resources	Read-only field that shows the total number of entries aggregated from Domino Directories after the Dircat task runs.
Packing density	Specifies the maximum number of Domino Directory entries that can be aggregated into each aggregate document. You usually do not have to change the default setting. Do not change the default setting if clients use local replicas of the directory catalog. For more information, see the earlier topic "Using performance settings in a condensed Directory Catalog."
Incremental fields	Specifies whether changed fields are stored in a temporary location. You usually do not have to change the default setting. Do not change the default setting if clients use local replicas of the directory catalog. For more information, see the earlier topic "Using performance settings in a condensed Directory Catalog."
Merge factor	If Incremental fields is enabled, controls the percent of total field changes that must occur before original fields in aggregate documents are updated. You usually do not have to change the default setting. Do not change the default setting if clients use local replicas of the directory catalog. For more information, see the earlier topic "Using performance settings in a condensed Directory Catalog."
Replication history	Shows the date and time when the Dircat task last aggregated the source directories listed in the field "Directories to Include." Click Clear History to do a full rebuild of the directory catalog. Do not click Clear History unless you understand Dircat rebuilds. For more information, see the later topic "The Dircat task."

4. Click File - Application - Properties. Choose how you want entries sorted.

Fields in Design tab	Description
Multilingual database	Leave this unchecked
Default language	Leave this unchecked
Default sort order	Specifies both the order that entries are stored in CDC documents and the ordering of document in CDC views. If you leave this blank, the Dircat task will use the default for your Domino task when it rebuilds the CDC. For more information, see the earlier topic "Setting the view sort order."
Unicode standard sorting	Uncheck this if you wish to use the default sort order. Check this box if the CDC will be either run on a server (step 5) or you want a language-insensitve sort ordering.

Note See the topic "Planning issues specific to condensed directory catalogs" section if you have different sets of users each wishing to have different sort orderings.

Step 4: Set up clients to use the condensed Directory Catalog

Use Desktop policy settings to automate setup of a condensed Directory Catalog on IBM® Lotus® Notes® clients. The automated setup creates a replica stub (an empty replica) of the directory catalog on the clients, with a replication schedule enabled to a replica of the directory catalog on a server that you specify. When the client replicates with a replica of the directory catalog on a server, a full-text index is created on the client replica after replication is complete. The automated setup process also adds the file name of the condensed Directory Catalog to the "Local address books" field in user preferences for mail, after the file name of the Person Address Book.

If you don't automate the directory catalog setup, you must create the replica and add the file name to clients manually.

Note User Setup Profiles used in Lotus Domino Release 5 for automated directory catalog setup continue to work in Lotus Domino 8.

To automate setup of a condensed Directory Catalog on clients:

1. (Optional) Create a replica of the condensed Directory Catalog on other servers. Then users have more choice of servers to use when they replicate to update their local replicas of the directory catalog. Domino creates a full-text index automatically on the replicas you create.

2. If you haven't already done so, create a Desktop policy settings document to use to automate setup of the directory catalog. Make sure you understand how to set up policies before you create a Desktop policy settings document.

3. From the Domino Administrator, click the Files tab, and open a replica of the directory catalog.

4. Choose Edit - Copy As Link - Application Link, then close the directory catalog.

5. Open the Desktop policy settings document you want to use to automate setup of the condensed Directory Catalog on clients.

6. Click the Databases tab, and then click the "Mobile directory catalogs" field.

7. Choose Edit - Paste to past the directory catalog database link into the "Mobile directory catalogs" field.

8. Click Save & Close.

Note Notes users should do pull replications regularly with up-to-date replicas of the directory catalog on servers.

Step 5: Set up servers to use the condensed Directory Catalog

Note It is strongly recommended that you use the Extended Directory Catalog on servers, as they provide faster and more flexible directory lookups.

Note Make sure the CDC has "Unicode standard sorting" enabled in the CDC's database properties design tab. See Step 3.

To set up a server to use a condensed Directory Catalog:

1. Create a replica of the built directory catalog on the server. Set up replication between the server and the Dircat server so that this server's replica of the directory catalog is kept up-to-date.

2. If necessary, from the Domino Administrator choose File - Open Server, to open the server you are setting up to use the directory catalog.

3. Click the Configuration tab.

4. In the left pane, expand Server - Current Server Document.

5. Click Edit Server.

6. On the Basics tab, in the "Name of condensed directory catalog on the server" field, enter the file name of the directory catalog replica you created on this server. If multiple servers use the same file name for their local replicas of the directory catalog, see the Tip below for a quick way to specify the file name.

7. (Optional) To allow the server to use all user names aggregated in the condensed Directory Catalog for client authentication, on the Basics tab of the Server document select "Trust the server based condensed directory catalog for authentication with internet protocols." If you don't want to trust the entire directory catalog for authentication, do not select this option.

Note To specify instead that the server trust for authentication names from only one or some of the directories aggregated in the directory catalog, in a directory assistance database used by the server, create a Directory Assistance document for each aggregated Domino Directory to trust that has a trusted rule enabled.

9. If necessary, wait for the Domino Directory changes to replicate to the server. Or force the replication.

10. Use the Restart Server command to Restart the server so it detects the changes to the Server document.

Tip If multiple servers use the same file name for their local replicas of the condensed Directory Catalog, you can specify that file name once in the Directory Profile of the domain Domino Directory, rather than multiple times in individual Server documents. To use the Directory Profile method, from the Domino Directory for the servers that will use the directory catalog, choose Actions - Edit Directory Profile and add the directory catalog file name to the "Directory catalog database name for domain" field. Then a server that doesn't have a directory catalog file name entered in its Server document uses the Directory Profile to find its local replica of the condensed Directory Catalog.

See also

Overview of setting up a condensed Directory Catalog
Benefits of condensed Directory Catalogs on clients (Mobile Directory Catalogs)
Planning directory catalogs
Directory Catalogs

Glossary