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.
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.
Table of replication settings
By default, two replicas exchange all edits, additions, and deletions if the servers the replicas are on have the necessary access. However, you can customize replication. For example, to save disk space, you can prevent the transfer of documents that are not pertinent to your site.

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.
    - How replication works
      For server-to-server or server to/from client replication, the Replicator on one computer calls another Domino® server at scheduled times. By default, the Replicator is loaded at startup. To schedule replication between servers, the servers must be able to connect to each other in order to update replicas. You may need to create Connection documents to enable server connections, depending on your server topology.
    - Guidelines for setting server access to databases
      For replication to occur properly, you must assign servers the appropriate access in the database ACL. Follow these guidelines when you set server access to databases.
    - Setting up a database ACL for server-to-server replication
      You add the names of servers to a database ACL in the same way that you add the names of people. The access level given to a server in an ACL determines what, if any, changes that server can replicate to the replica.
    - Creating replicas using the Administration Process
      Through the HCL Domino® Administrator you can use the Administration Process to initiate the creation of one or more replicas. You can create replicas on servers in the same domain or in another domain (across domains, using a cross domain administration request).
    - Table of replication settings
      By default, two replicas exchange all edits, additions, and deletions if the servers the replicas are on have the necessary access. However, you can customize replication. For example, to save disk space, you can prevent the transfer of documents that are not pertinent to your site.
      - Limiting the contents of a replica
        You can use replication settings to limit the size of a replica or to display a subset of information relevant to a particular group of users.
      - Limiting what a replica sends
        You can limit what one replica sends to other replicas by setting the following replication settings.
      - Assigning miscellaneous replication settings
        The Other panel of the Replication Settings dialog box includes these miscellaneous settings.
      - Specifying replication settings for a single replica
        You can specify replication settings for a replica as you create it or you can modify replication settings on an existing replica.
      - Specifying replication settings for multiple replicas from one source
        You can customize replication settings for multiple replicas of a database from one central source replica and then replicate these custom settings to the appropriate replicas. This approach to customizing replication allows you to centralize replication management and requires that you know the replication requirements for each replica.
      - Examples of specifying replication settings for multiple replicas
        There are different settings you can use when replicating to other servers. Do not use the server's common name when replicating servers. Only the server's full hierarchical name should be used during server-to-server replication. This applies to all instances of server-to-server replication. For example, when replicating from the server console, Connection documents, or from the Domino® Administrator.
    - Scheduling times for replication
      Whenever possible, schedule replication for times when there is less activity on the network -- before or after work or at lunch time.
    - Scheduling server-to-server replication
      For replication to occur between two servers, you create a Connection document that specifies how and when the information exchange occurs. Connection documents are stored in the Domino® Directory. Use only one Connection document at a time to handle all replication between each pair of servers. Creating unnecessary Connection documents increases network traffic and congestion.
    - Customizing server-to-server replication
      You can customize replication in several ways.
    - Viewing replication schedules and topology maps
      You can see a graphical representation of each server's replication schedule at a glance with the Domino® Administrator. Each server's replication schedule appears separately, even if the server is a member of a group listed in the Destination server field in a Connection document.
    - Database.nsf.replicate statistics
      Domino® maintains statistics about replication status.
    - Configuring managed replicas
      An administrator can use the Managed Replicas tab in the Desktop Settings document to set a policy that, for users affected by the policy, marks any existing local mail replica as a managed replica, and, if desired, creates a new managed replica if no local replica exists.
  - 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.

Table of replication settings

By default, two replicas exchange all edits, additions, and deletions if the servers the replicas are on have the necessary access. However, you can customize replication. For example, to save disk space, you can prevent the transfer of documents that are not pertinent to your site.

You can specify replication settings on a new replica as you create it or on an existing replica. You can specify some replication settings for multiple replicas at once from a central source replica. You must have Manager access to a replica to set replication settings for it.

Note: Replication settings are not intended to be used as a security measure.

Table 1. Replication setting options
Setting	Controls	Panel option
Remove documents not modified in the last x days	When Domino® purges document deletion stubs and, optionally, unmodified documents	Space Savers
This replica includes deletion stubs for all documents deleted since x	The cutoff date, which a replica uses to purge document deletion stubs deleted prior to the date and, optionally, unmodified documents Which documents are scanned during the first replication after clearing the replication history Note: By default, this date is periodically updated based on the number set for Remove documents not modified in the last `x` days.	Other
Receive summary and 40KB of rich text only	The size of documents that a replica receives	Space Savers
Replicate only a subset of the documents	Which documents a replica receives	Space Savers Advanced
Receive these documents from other replicas	Which non-document elements this replica receives	Advanced
Send deletions made in this replica to other replicas	Whether a replica can send document deletions to other replicas	Send
Send changes in application title and catalog info to other replicas	Whether a replica can send changes to the application title and Application Catalog categories to other replicas	Send
Send changes in local security property to other replicas	Whether a replica can send changes to the Encryption database property (in the Basics tab of the Application Properties box) to other replicas	Send
Temporarily disable replication for this replica	Whether a replica can replicate	Other
Set scheduled replication priority for this replica	The replication priority of a database used in Connection documents for scheduling replication	Other
CD-ROM publishing date	The publishing date for a database on a CD-ROM	Other