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.
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.

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.
  - Managing users
    The Administration Process helps you manage users by automating many of the associated administrative tasks. For example, if you rename a user, the Administration Process automates changing the name throughout databases in the Notes® domain by generating and carrying out a series of requests, which are posted in the Administration Requests database.
  - 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.
    - 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.
  - 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.
  - 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.
  - 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.
- Editing the NOTES.INI file
  You should rarely, if ever, need to modify a server's or client's NOTES.INI file. The NOTES.INI file contains many settings that Domino® and Notes® rely on to work properly. An accidental or incorrect change may cause Domino or Notes to run unpredictably. Therefore, you should edit the NOTES.INI file only if special circumstances occur or if Support recommends that you do so.
- 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.

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.

Assign an access level that is at least as high as the highest user access level

For example, design changes made to the replica on Server A replicate to Server B only if the replica on Server B gives Server A at least Designer access.

Include servers in read access lists for database design elements

If a database design element has a read access list associated with it that allows access only to certain users with Reader access, include the names of replicating servers in the read access list in addition to the server names with Reader access in the database ACL. For example, if a replica on Server A includes a form access list that limits who can read documents created with the form, include Server B in the read access list and give Server B at least Reader access in the ACL to allow Server B to pull new documents and changes to documents created with the form.

Assign appropriate access to intermediate servers

If replication occurs through an intermediate server, the intermediate server acts first as a destination server, then as a source server and must have the access level necessary to pass along the changes. For example, if you want ACL changes on Server A's replica to replicate to Server C by way of Server B, Server B's replica must give Manager access to Server A, and Server C's replica must give Manager access to Server B.

Assign Reader access for one-way replication

Give a server Reader access to a replica when you want to allow the server to receive information from the replica but not to send changes back. For example, to allow Server B to receive changes from a replica on Server A but not to send changes to Server A, give Server B Reader access to the replica on Server A.

Assign Editor access to allow author changes to replicate

If a replica includes an Authors field that allows authors to modify their own documents, a server must have at least Editor access, not Author access, to replicate these modifications. For example, changes made to Server A's replica by someone with Author access only replicate to Server B if Server B's replica gives Server A at least Editor access.