Home
IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
Configuring
Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
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.
Customizing server-to-server replication
You can customize replication in several ways.
Using multiple replicators
If you create Connection documents that schedule a server for multiple simultaneous or overlapping replications with different destination servers, set up multiple replicators to handle the replication sessions simultaneously. Multiple replicators efficiently use server resources, shorten replication cycles (especially in hub servers), and save replication time.

IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
- What's new in IBM® Domino® 10?
  Learn about all of the new features for administrators in IBM® Domino® 10.
- Overview
  Welcome to IBM® Domino® Administrator Help.
- Installing
  Use this documentation to install the IBM® Domino® server and subsequently deploy the IBM Notes® client.
- Planning
  Use this topic as an overview of planning task.
- Configuring
  Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
  - Configuring a network
    This section presents the planning concepts and setup procedures necessary for a successful IBM® 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 IBM® 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.
        Specifying replication direction
        When you choose replication direction, you identify which server(s) send and receive changes. The direction you choose does not affect or restrict the functionality of the replication process itself.
        Replicating only specific databases
        By default, Domino® replicates all databases that two servers have in common, but you can specify databases to be replicated.
        Replicating databases by priority
        Database managers assign a replication priority to databases so that Domino® administrators can schedule replication for databases based on priority.
        Limiting replication time
        Limiting the time a server has to replicate with another server prevents extensive replication sessions and allows you to control the cost of replication with servers in remote sites. For example, if replication depends on a slow connection and the database takes time to replicate, you can limit how long the replication period lasts.
        Using multiple replicators
        If you create Connection documents that schedule a server for multiple simultaneous or overlapping replications with different destination servers, set up multiple replicators to handle the replication sessions simultaneously. Multiple replicators efficiently use server resources, shorten replication cycles (especially in hub servers), and save replication time.
        Refusing replication requests
        To prevent a server from accepting a request for replication, edit the NOTES.INI file to include the setting ServerNoReplRequests. If this setting is set to 1, the called server refuses all replication requests.
        Forcing immediate replication
        You can replicate changes to critical databases, such as the Domino® Directory, without waiting for a scheduled connection. After you create Connection documents to schedule server-to-server replication, you can use a server command to force immediate replication.
        Disabling database replication
        You can disable replication of a database -- for example, to stop replication while you troubleshoot problems. Then, after you correct the problem, enable replication again. You can disable and enable replication of a single database, or if you use the Domino® Administrator, you can disable and enable replication of multiple databases at once.
        Forcing a server database to replicate
        Replication between database replicas on servers typically occurs according to schedules in Connection documents. However, there are times when you want to force replication between two replicas, rather than wait for replication to occur on schedule. For example, you might force replication when you want to test replication settings or troubleshoot replication problems.
      - 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 IBM® 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 IBM® Support Services recommends that you do so.
  - Configuring directory services
    This section describes how to plan, set up, and use IBM® 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®
    IBM® iNotes® (previously IBM Domino® Web Access) provides IBM 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 IBM iNotes.
  - Configuring Web servers
    This section describes how to set up the IBM® Domino® Web server, the Domino Web Navigator, and other Web servers such as IBM HTTP.
  - 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.
- Securing
  This section describes IBM® Domino® security features, including execution control lists, IDs, and SSL.
- Administering
  This documentation provides information about the administration tools for managing and monitoring IBM Domino® servers and databases.
- Tuning
  Use this information to improve IBM® Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
- Troubleshooting
  This section describes how to find and solve problems with IBM® Domino® server and Administrator client.
- Glossary

Using multiple replicators

If you create Connection documents that schedule a server for multiple simultaneous or overlapping replications with different destination servers, set up multiple replicators to handle the replication sessions simultaneously. Multiple replicators efficiently use server resources, shorten replication cycles (especially in hub servers), and save replication time.

About this task

When you use multiple replicators, each replicator handles only one replication session at a time. For example, if Hub-E/East/Renovations is scheduled to replicate with HR-E/East/Renovations and with Hub-W/West/Renovations simultaneously, one replicator handles replication between Hub-E/East/Renovations and HR-E/East/Renovations, while a second replicator handles replication between Hub-E/East/Renovations and Hub-W/West/Renovations.

Multiple replicators handle multiple replications between one source server and multiple destination servers simultaneously. Multiple replicators do not handle replications of multiple individual databases on a source server with a single destination server. For example, if both Database 1 and Database 2 on Hub-E/East/Renovations need to replicate with Hub-W/West/Renovations, only one replicator handles each replication session, one at a time.

Examine the Connection documents that schedule replication on each server. By adjusting the schedules and enabling multiple replicators, you can shorten the time it takes to complete a replication cycle. With this shortened cycle, you can schedule one or more additional cycles per day, which means fewer database updates and speedier replications per cycle. After you start multiple replicators, you can use the Tell command to stop all replicators; however, you cannot use the Tell command to stop a specific replicator.

Enable multiple replicators as follows:

From the NOTES.INI file -- Edit the Replicators or ServerTasks setting.
From the console -- Enter the Load Replica command at the console. Use this method if you need more replicators and you do notwant to shut down the server to edit the NOTES.INI file. Each time you enter this command, the server loads another replicator.