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.
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 Domino® Directory template
The default Domino® Directory template (PUBNAMES.NTF) controls the appearance and functionality of the Domino Directory database (NAMES.NSF). Domino uses the forms and settings in the default Domino Directory template to control features -- for example, mail, server tasks, and access control -- and to store critical information that manages server connections, mail routing, and system configuration.
Using the Domino® Directory to extend the LDAP schema
To add schema elements to the Domino® LDAP schema, you can create forms and subforms in the Domino Directory, or you can use the Domino LDAP Schema database (SCHEMA.NSF).
Using the Domino® Directory to create a new LDAP structural object class
You can add a form and associated subforms to the Domino® Directory to define a new LDAP structural object class in the LDAP schema and to enable documents created from the form to be LDAP-accessible. The preferred method for extending the schema is to use the Domino LDAP Schema database, however. Use the Domino Directory to extend the schema only if Notes® or Web users require access to the new entries defined by the schema elements through documents in the directory.
Creating and inserting a $xxxInheritableSchema subform
After you create a form to define a new structural object class, create an associated $xxxInheritableSchema subform and insert it into the form. The $xxxInheritableSchema subform defines the attributes for the structural object class.

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.
      - Setting up the Domino® Directory for a domain
        After you install and set up servers in a Domino® domain, you set up the Domino Directory for the domain by performing tasks including creating a central directory architecture, controlling access to the directory, categorizing users by corporate hierarchy, setting up Notes® clients to use a directory server, customizing the Directory Profile, and scheduling replication.
      - Controlling access to the Domino® Directory
        You control access to the HCL Domino® Directory by setting it overall in the ACL, assigning administrators to roles that correspond to their administrative tasks, and, if you want, controlling access to individual documents or using the extended ACL to set access at the form and field level.
      - Corporate hierarchies
        You can categorize a Person document in the HCL Domino® Directory by a corporate hierarchy. When an HCL Notes® user selects a name from a Domino Directory, the user can view the list of names by the assigned Corporate Hierarchy.
      - Setting up Notes® clients to use a directory server
        You can set up Notes® clients to use a different server from their mail servers for mail addressing. Type-ahead addressing searches a directory server only when Notes users do not use condensed (mobile) directory catalogs. Directory servers are not used for LDAP directory searches initiated by Notes users.
      - Customizing the Directory Profile
        Use the Directory Profile to specify miscellaneous settings for the HCL Domino® Directory.
      - Scheduling replication of the Domino® Directory
        Create Connection documents to schedule replication of the Domino® Directory on all servers in the Domino domain. Since the Domino Directory is central to a Domino system, it's important to replicate it frequently. Although the replication schedule you select ultimately depends on the configuration of the servers in the domain, in general, replicate the Domino Directory at least every 30 minutes or, if the directory is large and changes frequently, every 10 to 15 minutes.
      - The Domino® Directory template
        The default Domino® Directory template (PUBNAMES.NTF) controls the appearance and functionality of the Domino Directory database (NAMES.NSF). Domino uses the forms and settings in the default Domino Directory template to control features -- for example, mail, server tasks, and access control -- and to store critical information that manages server connections, mail routing, and system configuration.
        Rules for customizing the Domino® Directory
        To avoid rendering Domino® inoperable, follow these rules when you customize the Domino Directory.
        Customizing the Domino® Directory template
        The HCL Domino® Directory template is supplied with the Domino server install kit and used to control aspects of the master Domino Directory, which controls client access to a variety of functionality.
        Creating a copy of the Domino® Directory template
        Never customize the default HCL Domino® Directory template (PUBNAMES.NTF). Instead, create a copy of the default Domino Directory template and then customize the copy.
        Customizing a visible view in the Domino® Directory
        Depending on how extensive your changes will be to the view, you can customize the view or a copy of the view. If your changes are minimal, customize the view instead of a copy. Then when you upgrade to a new version of the default HCL Domino® Directory template, you must re-create the customization. If your changes will be extensive, customize a copy of the view. Then when you upgrade to a new version of the Domino Directory template, you need only to reapply the customization.
        Using the Domino® Directory to extend the LDAP schema
        To add schema elements to the Domino® LDAP schema, you can create forms and subforms in the Domino Directory, or you can use the Domino LDAP Schema database (SCHEMA.NSF).
        Using the Domino® Directory to create a new LDAP structural object class
        You can add a form and associated subforms to the Domino® Directory to define a new LDAP structural object class in the LDAP schema and to enable documents created from the form to be LDAP-accessible. The preferred method for extending the schema is to use the Domino LDAP Schema database, however. Use the Domino Directory to extend the schema only if Notes® or Web users require access to the new entries defined by the schema elements through documents in the directory.
        Creating a form to define a new LDAP structural object class
        You can use the HCL Domino® Directory to create a new structural object class.
        Creating and inserting a $xxxInheritableSchema subform
        After you create a form to define a new structural object class, create an associated $xxxInheritableSchema subform and insert it into the form. The $xxxInheritableSchema subform defines the attributes for the structural object class.
        Creating and inserting a $xxxExtensibleSchema subform
        After you create and insert a $xxxInheritableSchema subform for structural object class, create and insert a $xxxExtensibleSchema subform into the $xxxInheritableSchema subform so that you can add an auxiliary object class to the structural object class.
        Configuring a new LDAP structural object class to inherit
        You can configure a new structural object class defined to inherit from another structural object class defined in the directory.
        Using the Domino® Directory to create an LDAP auxiliary object class
        Use an auxiliary object class to add one set of attributes to multiple structural object classes. To use the Domino® Directory to create an LDAP auxiliary object class, create a subform to define the auxiliary object class, and then insert the subform into the $xxxExtensibleSchema subform of each structural object class to which you want to add the auxiliary object class. The superior object class for an auxiliary object class you add is Top.
        Using the Domino® Directory to define an LDAP attribute for a new object class
        The preferred method for extending the LDAP schema is to use the Domino® LDAP Schema database. Use the Domino Directory to extend the schema only if Notes® or Web users require access to the new schema elements through documents in the directory.
        Applying template customization to the Domino® Directory database
        After you customize a copy of the HCL Domino® Directory template, you must complete this procedure to apply the design changes to the Domino Directory database, which is usually (NAMES.NSF).
    - 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).
    - 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.

Creating and inserting a $`xxx`InheritableSchema subform

After you create a form to define a new structural object class, create an associated $xxxInheritableSchema subform and insert it into the form. The $xxxInheritableSchema subform defines the attributes for the structural object class.

Before you begin

Make sure that you are working in a copy of the HCL Domino® Directory template (for example RENOVATIONSNAMES.NTF) and that you have Designer or Manager access in the ACL.

Procedure

From HCL Domino® Designer, open RENOVATIONSNAMES.NTF.
Do the following to copy the contents of the $countryInheritableSchema subform into a new subform:

Important: Do not select the $countryInheritableSchema subform and use copy and paste to copy it.
1. In the navigation pane, select Shared Elements and then Subforms.
2. Open the $countryInheritableSchema subform, choose Edit > Select All, then Edit > Copy.
3. Close the $countryInheritableSchema subform.
4. With Subforms still selected, right-click New Subform. For the form name, type $xxxInheritableSchema, where xxx is the name of the new structural object class created previously, for example, $renovationsPrinterInheritableSchema. Click OK.
5. Choose Edit > Paste.
Do the following to specify the properties for the new subform:
1. With the new subform open, choose Design > Subform Properties.
2. Deselect the Options property Render pass through HTML in Notes.
3. Leave the other properties the same, and close the Subform Properties box.
On the Mandatory tab, do the following:
1. Delete the field OfficeCountry and its label. Do not delete the $dspType field and label.
2. Choose Create > Field.
3. Next to the Name property, specify FullName.
4. Next to the Type property, select Names.
5. Close the Field box.
6. Select Input Validation in the Object pane, and enter the following formula:
```
@V2If(FullName = ""; @Failure("FullName is required"); @Success)
```
Optional: On the Optional tab, delete the searchGuide field and its label, and optionally delete the comment field and its label.
Leave the Operational tab as is.
Define the mandatory and optional attributes for the new structural object class in the new InheritableSchema subform.
Do the following to remove the $countryExtensibleSchema subform from the new InheritableSchema subform:
1. On the Extensible tab of the new InheritableSchema subform, place the cursor the equivalent of one line down to select the $countryExtensibleSchema subform.
2. Verify that the $countryExtensibleSchema subform is selected. Click Edit > Delete to remove the $countryExtensibleSchema subformfrom the new InheritableSchema subform.
Save and close the new InheritableSchema subform.
Do the following to insert the new InheritableSchema subform into the form created to define the structural object class:
1. From Domino® Designer, open RENOVATIONSNAMES.NTF.
2. In the navigation pane, select Forms and open the form you created previously -- for example, renovationsPrinter.
3. Position the cursor between the form name and the Type, Owner, LocalAdmin, and DocumentAccess fields.
4. Choose Create > Resource > Insert Subform, select the InheritableSchema subform you created -- for example $renovationsPrinterInheritableSchema -- and click OK.
Save and close the form.

What to do next

Complete the procedure Creating and inserting an $xxxExtensibleSchema subform.