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.
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.
Using directory assistance in a cluster
A server can use directory assistance to look up information in a directory other than its local primary Domino® Directory. The directory can be a remote LDAP directory or a local or remote replica of any of the following types of Domino directories: a secondary Domino Directory, an Extended Directory Catalog, or a primary Domino Directory. To configure directory assistance, you create a directory assistance database. This database contains information about directories on other servers and how to connect to them.

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.
- 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.
  - Creating a cluster
    A cluster is a group of application servers that you manage together as a way to balance workload. If possible, use the administration server when you create a cluster. This makes the creation process faster. The administration server does not have to be part of the cluster.
  - Verifying that the cluster was created correctly
    There are a number of ways you can check that the cluster was created correctly.
  - Managing user access to databases
    Users should have the same access rights in all replicas of a database in the cluster. Otherwise, if users fail over to a replica for which they have fewer access rights, they may be denied access, or they may not see the same documents or be able to perform the same functions as in the original database they were using.
  - Creating replicas in a cluster
    To create replicas in a cluster, you use the same Administration Process you would use to create replicas on any server.
  - Using symmetrical clusters
    A symmetrical cluster ensures that HCL Notes® databases remain identical across all servers in a cluster. A repair service repairs missing or damaged databases by replacing them with good copies from donor cluster members.
  - Setting up mail in a cluster
    Mail routing fails over if the recipient's mail server is not available when the router attempts to deliver the mail. As long as the mail server is in a cluster, the router delivers the mail to another cluster server that contains a replica of the recipient's mail database. Thus, the recipient continues to receive mail.
  - Using scheduled replication in a cluster
    You should run standard replication on a regular basis. The number of times per day you run standard replication depends on how important it is for you to keep all replicas synchronized. In most cases, once or twice per day is sufficient. If it is absolutely critical to keeps data synchronized at all times, you may want to replicate every hour or two.
  - Replicating with all servers in a cluster
    An additional benefit of creating a cluster is that it can simplify your replication topology and increase the reliability and performance of replication. This is because you can set up a server outside the cluster to replicate with all the servers inside the cluster. You do this by creating a single Connection document that specifies the server outside the cluster as the source of replication and the cluster name as the destination of replication. Then, every database on the source server that has a replica in the cluster replicates. If the cluster contains more than one replica of a database, the source server replicates with only one of those replicas, and cluster replication propagates the changes to the other replicas in the cluster.
  - Enabling the display of cluster replication status messages
    You can tell the Cluster Replicator to display status messages on the server console.
  - Obeying database size quotas during cluster replication
    To make sure that replicas will be identical when users fail over, cluster replication ignores database size quotas by default. This makes cluster replication consistent with the router, which also ignores quotas by default. If you want cluster replication to obey database size quotas, follow these steps.
  - Using directory assistance in a cluster
    A server can use directory assistance to look up information in a directory other than its local primary Domino® Directory. The directory can be a remote LDAP directory or a local or remote replica of any of the following types of Domino directories: a secondary Domino Directory, an Extended Directory Catalog, or a primary Domino Directory. To configure directory assistance, you create a directory assistance database. This database contains information about directories on other servers and how to connect to them.
  - Setting up roaming servers in a cluster
    Configure a cluster of servers to support Notes® roaming users. Make sure that replicas of each user's roaming files are on at least two roaming servers in the cluster. When a user tries to access roaming files on a server that is not available, Domino® fails over to a different cluster server that has replicas of the user's roaming files.
  - Setting up cluster access for remote users
    You can give remote users the benefits of a cluster by setting them up to access the cluster through a pass-through server. The pass-through server can redirect the users to a different server in the cluster if the original server is busy or not available. Unless you use a pass-through server, users will have to dial each cluster server individually and will not fail over if the server they call is not available.
  - Using the Server Web Navigator in a cluster
    If you plan to use the Server Web Navigator in a cluster, be sure that the Web databases (WEB.NSF) on the cluster servers are replicas. Since the Web database is generated automatically when you start the Server Web Navigator, it is a common error for the clustered servers to contain Web databases that are not replicas of each other. Therefore, these databases do not fail over to each other.
  - Setting up a private LAN for a cluster
    Setting up a private LAN for your cluster separates the server probes and cluster replication from the rest of your network traffic. This prevents the cluster traffic from slowing down your primary network.
  - Clustering Domino® servers that run Internet protocols
    You can configure and use the Internet Cluster Manager (ICM) to extend the benefits of HCL Domino® clusters to HTTP clients and Domino Web servers. You can also employ an alternative method of using failover with HTTP servers, as well as methods to use failover with POP3, IMAP, and LDAP servers.

Using directory assistance in a cluster

A server can use directory assistance to look up information in a directory other than its local primary Domino® Directory. The directory can be a remote LDAP directory or a local or remote replica of any of the following types of Domino® directories: a secondary Domino® Directory, an Extended Directory Catalog, or a primary Domino® Directory. To configure directory assistance, you create a directory assistance database. This database contains information about directories on other servers and how to connect to them.

If you try to access the directory assistance database on a cluster server that is unavailable, Domino® fails over to a replica of the database, if one is available in the cluster. When you use directory assistance in a cluster, be sure you use replicas of the same directory assistance database on all cluster servers that contain a replica. This is important so that Name Lookups fail over correctly.

When the directory assistance database refers to a Domino® directory on a cluster server, you can configure Domino® to use one of two failover methods for directory assistance: directory assistance failover or cluster failover. When you use directory assistance failover, Domino® fails over to one of the servers that you list as having a replica of the directory. Domino® does not take into account the current workload of the servers. When you use cluster failover, Domino® checks the workload of the servers and then fails over to the least busy cluster server that contains a replica of the directory.