Planning
Use this topic as an overview of planning task.
- Roadmap for deploying Domino® servers
  Use this as a tool when planning how to integrate HCL Domino® into your existing environment.
- Planning server-to-server connections
  Servers must connect to each other to exchange data, for example to replicate databases and exchange mail. You can create connections between servers across a local area network (LAN) or wide area network (WAN), by using a pass-through server (a server that acts as an intermediary server between a client and its destination), or over the Internet. Create a Server Connection document whenever you need to establish any new or additional server connections. You can modify this document when necessary.
- Planning directory services
  HCL Domino® provides a range of directory service features.
  - Using directory servers in a Domino® domain
    An HCL Domino® domain is a network of clients and servers whose users, servers, connections, and access control information is described in a single database called the Domino Directory. When you set up the first server in an organization, Domino creates a Domino domain and a Domino Directory for the domain. When you add servers to the domain they pull replicas of the Domino Directory. To create an additional domain and Domino Directory, you perform a first server setup.
  - Using a central directory architecture in a Domino® domain
    A central directory architecture is an optional directory architecture you can implement in an HCL Domino® domain. This architecture differs from the traditional distributed directory architecture in which every server in a domain has a full replica of the primary Domino Directory.
  - Planning LDAP features
    Lightweight Directory Access Protocol (LDAP) is a standard Internet protocol for searching and managing entries in a directory.
  - Planning directory access control
    Use the database ACL to control the general access that users and HCL Domino® servers have to the Domino Directory. Optionally, use an extended ACL to refine the general database ACL and further restrict access to specific portions of the directory. An extended ACL is available for only a Domino Directory and an extended directory catalog.
  - Planning new entries in the Domino® Directory
    The tools you can use to add entries to the HCL Domino® Directory are the HCL Notes® user registration program, migration tools that are integrated with the Notes user registration program, Domino directory synchronization tools, and third-party LDAP applications. You can also add an entry manually, for example you typically add a group entry manually. You might also develop a custom Notes application to add entries.
  - Planning the management of entries in the Domino® Directory
    You can use the HCL Domino® Administrator, directory synchronization tools, and third-party LDAP applications to manage entries in the Domino Directory.
  - Planning directory services for Notes® clients
    There are a variety of directory services features available to HCL Notes® clients.
  - Planning directory services in a multiple-directory environment
    HCL Domino® provides directory catalogs and directory assistance to help companies operate in environments with secondary directories.
  - Planning internationalized directory services
    Options are provided for internationalized directory services.
  - Planning directory customization
    You can add forms and views to the HCL Domino® Directory to accommodate specific needs of your company. If you use the LDAP service, you can also use the Domino LDAP Schema database (schema.nsf) to define new object classes and attributes to be added to the directory.
  - Directory services terms
    This topic is an overview of Domino terminology around directory services.
- Planning a mail routing topology
  HCL Domino® offers you considerable flexibility in configuring your mail system infrastructure, allowing you to use HCL Notes® routing, SMTP routing, or both, for internal and external messages.
- Planning a cluster
  When planning a cluster, it is important to consider the performance and ability of your hardware. The cluster must have enough CPU power, memory, and disk space to handle the cluster traffic and the number of databases and replicas required.
- Planning the TCP/IP network
  The default TCP/IP configuration for an HCL Domino® server is one IP address that is globally bound, meaning that the server listens for connections at the IP addresses of all NICs on the computer. Global binding works as long as the computer does not have more than one IP address offering a service over the same assigned TCP port.
- Messaging overview
  The HCL Domino® mail system has three basic components: Domino mail servers, Domino mail files, and mail clients. The Domino mail server is the backbone of an organization's messaging infrastructure, acting both as an Internet mail server and an HCL Notes® mail server. Domino provides standards-based Internet messaging through its support of the Simple Mail Transfer Protocol (SMTP), Post Office Protocol version 3 (POP3), Internet Message Access Protocol (IMAP), and Multipurpose Internet Mail Extensions (MIME). At the same time, Domino supports Notes mail through the use of Notes routing protocols -- Notes remote procedure calls (NRPC) -- and the Notes rich text message format.
- Planning your Notes® client deployment
  Use the references listed here to plan for, install, upgrade to, and configure the HCL Notes® client.
- Planning security
  An important aspect of planning security for your Domino® environment is understanding the tasks and features involved with securing each type of resource.

Planning directory customization

You can add forms and views to the HCL Domino® Directory to accommodate specific needs of your company. If you use the LDAP service, you can also use the Domino® LDAP Schema database (schema.nsf) to define new object classes and attributes to be added to the directory.

Some of the questions to ask when planning directory customization are:

To define a new type of entry in the directory, should you use the Schema database or create a form in the Domino® Directory instead? If you don't use the LDAP service, you must create a form. If you use the LDAP service you can use the Schema database to define object classes and attributes with some LDAP-specific characteristics that are not available when you create Domino® Directory forms. However only LDAP clients, not Notes® and Web clients, can access entries defined only in the Schema database.
If you use the LDAP service, are there attributes and object classes already defined in the Domino® LDAP schema that serve your company's needs? The schema -- the types of directory entries that are defined for the LDAP service -- by default defines many object classes and attributes which you may be able to use rather than adding new ones.
If your company doesn't use the LDAP service, should you create a form in such a way that it can represent an LDAP object class? It's good practice to create a form that can represent an LDAP object class, so that if in the future your company uses the LDAP service, the design requirements are in place.