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.
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.
Planning the Domain Index
Because the initial process of spidering databases and file systems and creating a full-text index for an entire Domino® domain can take days or even weeks, it is important to plan carefully before starting the indexing server. The more you have thought about what data sources should be indexed, how they should be categorized in the Domain Catalog and search form, and how much space your Domain Index requires, the less work you will have to do.
Estimating the size of the Domain Index
The size of a Domain Index is related to the size of the data being indexed, not to the size of the database. A small database with a lot of text can generate a larger index than a large database that has a lot of design elements. There is no easy way to measure the data in a database, but you can use a percentage of database size to estimate the size of the Domain Index.

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.
  - 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.
    - Server configurations for Domain Search
      This topic describes required and optional configurations for the servers you use for Domain Search.
    - Planning the Domain Index
      Because the initial process of spidering databases and file systems and creating a full-text index for an entire Domino® domain can take days or even weeks, it is important to plan carefully before starting the indexing server. The more you have thought about what data sources should be indexed, how they should be categorized in the Domain Catalog and search form, and how much space your Domain Index requires, the less work you will have to do.
      - The Domain Catalog
        The Domain Catalog, a database that uses the CATALOG.NTF template, controls which databases and file systems get indexed for Domain Search. Even if your organization is not implementing Domain Search, the Domain Catalog is a useful administrative tool for such tasks as keeping track of the location of database replicas.
      - Assigning database categories for the Domain Search form
        On the Design tab of the Database Properties box, you can assign one or more categories to each database to be included in the Domain Index. These categories appear on the search form to provide a user with a way to narrow a search. Categories are also displayed in views of the database catalog and Domain Catalog.
      - Estimating the size of the Domain Index
        The size of a Domain Index is related to the size of the data being indexed, not to the size of the database. A small database with a lot of text can generate a larger index than a large database that has a lot of design elements. There is no easy way to measure the data in a database, but you can use a percentage of database size to estimate the size of the Domain Index.
      - Adding a database to the Domain Index
        If an application database will be useful to a wide audience, include the database in the Domain Index.
      - Excluding attachments from the Domain Index
        The following types of attachments are excluded from the Domain Index by default: .*.ap,*.au,*.bkf,*.bqy,*.cab,*.cca,*.dbd,*.dll,*.exe,*.gif,*.gz,*.img,*.jar,*.jpg,*.lwp,*.m4p,*.m4v,*.MIF,*.mov,*.mp3,*.mp4,*.mpg,*.msi,*.nsf,*.ntf,*.p7m,*.p7s,*.pag,*.pdb,*.pic,*.png,*.pst,*.rar,*.shw,*.sys,*.tar,*.tar,*.tif,*.wav,*.wmf,*.wpl,*.wq1,*.z,*.zip
      - Domain Search security
        When a user performs a Domain Search on Domino® databases, Domain Search checks each result against the ACL of the database in which the result was found to verify that the user has access to read the document. To perform this check, the Domain Catalog contains a listing for all databases that includes each database's ACL. For Domino to include a link to a result document in a user's result set, the user must have the necessary access to read the document -- that is, have at least Reader access to the database that includes the document and be included in the Readers field, if the document has one.
    - Creating and updating the Domain Index
      The indexing server relies on the Domain Catalog to tell it which databases and file systems to include in the Domain Index. You use the Server document to enable the Domain Indexer task and set a schedule for it to run. By default, the Domain Indexer task runs once an hour.
    - Customizing Domain Search forms
      Domain Search includes several default forms, including forms for searching, specifying file systems, and presenting results. Both the search and results forms can be customized to suit organization-specific needs. An application developer can, for example, add a corporate logo to either form, or rearrange the fields.
    - Setting up Notes® users for domain search
      Notes® client and Web users can search an entire Domino® domain for application documents, files, and attachments that match a search query. Notes client users can perform domain searches as soon as you add the designated indexing server to the Catalog/domain search server field in their Location documents.
    - Setting up Web users for Domain Search
      For Web users to have access to Domain Search functionality, the indexing server, as well as all the servers being spidered by the indexer, must be set up as Domino® Web servers.
    - Using content maps with Domain Search
      Content maps let users browse for information rather than search for it using full-text search. Content maps organize documents by topics, or content, into categories.

Estimating the size of the Domain Index

The size of a Domain Index is related to the size of the data being indexed, not to the size of the database. A small database with a lot of text can generate a larger index than a large database that has a lot of design elements. There is no easy way to measure the data in a database, but you can use a percentage of database size to estimate the size of the Domain Index.

About this task

You can use the hidden view $MultiDbIndex in the Domain Catalog to find the sizes of all databases selected for indexing. You can also use this view to find out which of these databases have already been indexed individually by their database managers -- and use full-text index size as a more accurate indicator of the space a database will take up in the Domain Index.

Procedure

From the Domino® Administrator, choose File > Application > Open.
Select the cataloging server for the domain, and then select Domain Catalog.
Hold down CTRL-SHIFT and click Open.
In the view pane, click ($MultiDbIndex).
For each database listed, double-click the database entry to display the Database Entry document.

Note: If more than one replica of a database is listed, the indexing server indexes the replica on the server you include in the Limit domain wide indexing to the following servers field when you create the index. If this field is blank, the indexing server indexes the replica with the greatest number of documents.
Do one of the following for each database set to be part of the Domain Index:
- If there is a value in the Number of bytes indexed field on the Full Text tab, record it.
- If there is no value in the Number of bytes indexed field, record a number between 20 and 40 percent of the value in the Database size field on the Database tab. Record 20 percent if the database is heavy on design, 40 percent if it is heavy on text.
Add the values from Step 6 to obtain an estimate of the Domain Index in bytes.

Tip: To convert your estimate to megabytes, divide by 1024 twice.