Home
Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
Configuring users and servers
Topics in this section describe how to set up users and servers.
Configuring directory services
This section describes how to plan, set up, and use HCL Domino® directory services.
Directory assistance
Directory assistance allows a server to look up information in a directory other than a local primary Domino® Directory (NAMES.NSF).
Directory assistance concepts
Before you set up directory assistance, read about these directory assistance concepts.
Directory assistance for the primary Domino® Directory
A server with a local replica of its primary Domino® Directory searches the directory automatically without the use of directory assistance.
Limiting directories to authentication-only lookups
You can limit the use of a directory to authentication.

Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Configuring a network
  This section presents the planning concepts and setup procedures necessary for a successful HCL Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
- Configuring users and servers
  Topics in this section describe how to set up users and servers.
  - Understanding the Server document
    The Server document is set up when you register a server. It contains many of the settings that define how your server operates.
  - Policies
    Use Domino® policy settings to control how users work with Notes®. A policy is a document that identifies a collection of individual policy settings. Policy settings documents define a set of defaults that apply to the users and groups to which the policy is assigned. You can change policy settings and they will be automatically applied to the assigned users and groups.
  - Defining default settings for Notes® user registration
    Before you register new Notes® users, you can specify default settings that apply to all users. Default settings simplify user registration and ensure user settings consistency. You can define many default settings, such as what mail server users have or what certifier ID to use for user registration. You can also specify a default workstation execution control list (ECL) to protect data from unauthorized workstation access.
  - Using groups
    Groups are lists of users, groups, and servers that have common traits. They are useful for mailing lists and access control lists. Using groups can simplify administration tasks.
  - Replicas
    You can make a database available to users in different locations, on different networks, or in different time zones, by creating replicas of the database.
  - Calendars and scheduling
    The calendar and scheduling features allow users to check the free time of other users, schedule meetings with them, and reserve resources, such as conference rooms and equipment.
  - Editing the notes.ini file
    The Domino and Notes notes.ini files contain the settings required for the server and client to operate correctly. If you modify or add settings in a notes.ini file, do so cautiously and never edit the file directly with a text editor.
  - Configuring directory services
    This section describes how to plan, set up, and use HCL Domino® directory services.
    - The Domino® Directory
      The Domino® Directory, which some previous releases referred to as the Public Address Book or Name and Address Book, is a database that Domino creates automatically on every server. The Domino Directory is a directory of information about users, servers, and groups, as well as custom entries you may add. Registering users and servers in a domain automatically creates corresponding Person documents and Server documents in the Domino Directory for the domain. These documents contain detailed information about each user and server.
    - The LDAP service
      Lightweight Directory Access Protocol (LDAP) is a standard Internet protocol for searching and managing entries in a directory, where an entry has one or more attributes associated with a distinguished name. A distinguished name -- for example, cn=Phyllis Spera,ou=Sales,ou=East,o=Renovations -- is a name that identifies an entry within a directory tree.
    - LDAP schema
      A directory entry contains information about a particular entity, or object -- for example, a person or a group -- and is associated with a distinguished name. An LDAP schema is a set of rules that define what can be stored as entries in an LDAP directory. Each LDAP directory has a default schema, which organizations can customize, or "extend," by adding elements to it. The elements of a schema are attributes, syntaxes, and object classes. LDAP directory servers provide the ability to enforce the schema to ensure that directory changes made using LDAP operations conform to it.
    - ldapsearch utility
      Domino® and Notes® provide a command-line search utility, LDAPSEARCH.EXE, that you use to search entries in any LDAP directory. The ldapsearch utility connects to a directory server and returns results that match search criteria you specify. It is available on Domino server and Notes client platforms.
    - Directory assistance
      Directory assistance allows a server to look up information in a directory other than a local primary Domino® Directory (NAMES.NSF).
      - How directory assistance works
        To configure directory assistance, you create a directory assistance database from the template DA.NTF, and replicate it to the servers that will use it. A server must have a local replica of a directory assistance database to use directory assistance. Then you add the database file name to the Directory Assistance database name field in the Domino® Directory Server documents of these servers.
      - Directory assistance services
        Before you set up directory assistance, read about the services directory assistance can provide.
      - Directory assistance concepts
        Before you set up directory assistance, read about these directory assistance concepts.
        Directory assistance and naming rules
        When you configure directory assistance for a directory, you define at least one naming rule that corresponds to the names of users in the directory. Naming rules are based on the X.500 distinguished name model. This model uses a directory tree name hierarchy of country (c), organization (o), and organizational unit (ou) to divide names into parts that together represent unique locations in the directory tree. This is also the naming model Domino® and Notes® have traditionally used.
        Directory assistance and domain names
        When you configure directory assistance for a directory you must configure a domain name for the directory that is unique within the directory assistance database. You use the Domain name field on the Basics tab of a Directory Assistance document to configure a directory's domain name.
        Directory assistance and failover for a directory
        When you set up directory assistance for a directory, you can configure failover for the directory.
        Directory assistance for an extended directory catalog
        Unless you integrate an extended directory catalog directly into a server's primary Domino® Directory, a server uses directory assistance look up information in an extended directory catalog.
        Directory assistance in conjunction with a condensed directory catalog
        Condensed directory catalogs are optimized for small size and client use. In this release of Domino®, using a condensed directory catalog on a server is no longer supported. If you created condensed directory catalogs and are using them on servers running earlier releases, they will continue to operate, but are not recommended.
        Directory assistance for the primary Domino® Directory
        A server with a local replica of its primary Domino® Directory searches the directory automatically without the use of directory assistance.
        Using directory assistance to control which replicas of a Domino® Directory server can be used
        A Configuration Directory is a small, selective replica of a domain Domino® Directory that contains only Domino configuration information. A server with a Configuration Directory looks up information related to directory services, such as information in user and group documents, in a full replica of the domain primary Domino Directory on a remote server.
        Using directory assistance to prevent the LDAP service from searching the primary Domino® Directory
        You can set up directory assistance for the primary Domino® Directory to prevent a server that runs the LDAP service from using the primary Domino Directory when processing LDAP requests. For example, you might want the LDAP service to use a secondary Domino Directory, but not the primary Domino Directory.
        Limiting directories to authentication-only lookups
        You can limit the use of a directory to authentication.
        Number of directory assistance databases
        Before you set up directory assistance, plan how many directory assistance databases to use. You can create and configure one directory assistance database that all or most servers use. Or you can create more than one directory assistance database, with groups of servers -- for example servers within a domain -- each using specific ones.
      - Setting up directory assistance
        To set up directory assistance in an Domino® domain, complete these procedures.
      - Directory assistance examples
        These examples illustrate directory assistance for one secondary Domino® Directory, for an extended directory catalog, and for an extended directory catalog and a remote LDAP directory.
    - Directory Sync
      Directory Sync allows you to sync people and group data from an external LDAP directory into the Domino® directory. Currently data from Active Directory can be synced.
    - Directory catalogs
      A directory catalog is an optional directory database that typically contains information aggregated from multiple Domino® directories. Clients and servers can use a directory catalog to look up mail addresses and other information about the people, groups, mail-in databases, and resources throughout an organization, regardless of the number of Domino domains and Domino Directories the organization uses.
    - Extended ACL
      An extended access control list (ACL) is an optional directory access-control feature available for a directory created from the PUBNAMES.NTF template -- a Domino® Directory or an extended directory catalog. An extended ACL is tied to the database ACL, and you access it through the Access Control List dialog box using a Notes® or Domino Administrator client.
  - Configuring messaging
    This section provides an overview of messaging and describes how to set up mail routing, how to set up and customize mail servers, and how to track mail.
  - Configuring iNotes®
    HCL iNotes® provides HCL Notes® users with browser-based access to Notes mail and to Notes calendar and scheduling features. Administrators specify mail policy and security policy settings as well as notes.ini file settings to complete the full implementation of HCL iNotes.
  - Configuring Web servers
    This section describes how to set up the HCL Domino® Web server, and the Domino Web Navigator.
  - Setting up a cluster
    Setting up a cluster includes the tasks of creating and verifying that it is working correctly, and then setting up user access, mail, replications, size quotas, directory assistance, roaming, web navigation, and use of a private LAN in the cluster.
  - Configuring Widgets and Live Text
    Widgets and Live Text enables end users to see and act on Live Text in supported documents, including HCL Notes® mail, using XML extensions (widgets) created specifically for their use.
  - Domain Search
    Notes® client and Web users can use Domain Search to search an entire Domino® domain for database documents, files, and attachments that match a search query.

Limiting directories to authentication-only lookups

You can limit the use of a directory to authentication.

You may need to deploy a directory for authentication purposes only if:

You have both an Domino® and an LDAP directory that contain some identical names.
You do not use the LDAP directory names for mailing.
Your mail clients are experiencing "Ambiguous name" dialog boxes when sending mail.

It is becoming common practice to use a corporate LDAP server to provide authentication (userid/password) services for single sign-on (SSO) purposes. Often, these LDAP servers are not configured, deployed, or intended to support mail routing (or other Domino-based) directory lookups.

Because Domino® does not support a universal name mapping scheme for Domino-style identities (fullnames or distinguished names of the form cn=xxxx, ou=yyyy, o=zzzz) and the less (or differently) constrained distinguished name formats that are implemented by various LDAP directories, deploying an LDAP directory to be used for authorization can cause name ambiguity problems with some Domino® services if duplicate entries exist in the native Domino® directories and the LDAP directory being deployed. Since duplicate entries are usually the case if the LDAP directory is being deployed to allow SSO, or to provide LDAP-based authentication for Internet services, it is necessary to avoid sending certain lookups to the LDAP directories. Otherwise, sending email can result in an a large number of unnecessary lookups to the LDAP directory, thereby decreasing performance.

You indicate that a directory should be used only for authentication on the Basics tab of the Directory Assistance document as follows:

Set Group Authorization to Yes or enable one of the Naming Contexts (Rules) as Trusted for Credentials. This reveals a new setting: Use exclusively for Group Authorization or Credential Authentication.
The default setting for Use exclusively for Group Authorization or Credential Authentication is No. Change it to Yes to limit searches on this directory strictly for authentication.

If neither setting is enabled, the directory will be searched.