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 your Domino server deployment
    Before you install and set up the first HCL Domino® server, you must plan server and organizational naming and security. If you are adding an additional server to an existing Domino infrastructure, you must have already registered the server and its server ID and password must be available.
  - Getting started with Domino® for IBM® i
    You can get information on install and deploying Domino® on an IBM® i server.
  - Functions of Domino® servers
    Before you install and set up the first Domino® server, consider the function and physical location of the servers that your company needs and determine how to connect the servers to each other.
  - Hierarchical naming for servers and users
    Hierarchical naming is the cornerstone of HCL Domino® security; therefore planning it is a critical task. Hierarchical names provide unique identifiers for servers and users in a company. When you register new servers and users, the hierarchical names drive their certification, or their level of access to the system, and control whether users and servers in different organizations and organizational units can communicate with each another.
  - Domino® domains
    A Domino® domain is a group of HCL Domino servers that share the same Domino Directory. As the control and administration center for Domino servers in a domain, the Domino Directory contains, among other documents, a Server document for each server and a Person document for each HCL Notes® user.
  - Partitioned servers
    Using Domino® server partitioning, you can run multiple instances of the Domino server on a single computer. By doing so, you reduce hardware expenses and minimize the number of computers to administer because, instead of purchasing multiple small computers to run Domino servers that might not take advantage of the resources available to them, you can purchase a single, more powerful computer and run multiple instances of the Domino server on that single machine.
  - Certifier IDs and certificates
    Certifier IDs and certificates form the basis of HCL Domino® security. To place servers and users correctly within your organization's hierarchical name scheme, you create a certifier ID for each branch on the name tree. You use the certifiers during server and user registration to "stamp" each server ID and user ID with a certificate that defines where each belongs in the organization. Servers and users who belong to the same name tree can communicate with each other; servers and users who belong to different name trees need a cross-certificate to communicate with each other.
  - Domino® server services
    Before you start the HCL Domino® Server Setup program, decide which services and tasks to set up on the server.
  - Domino® naming requirements
    Refer to these guidelines when naming parts of the HCL Domino® system.
  - Building the Domino® environment
    After installing the first HCL Domino® server and any additional servers, configure the servers and build the 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.
- 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.

Roadmap for deploying Domino® servers

Use this as a tool when planning how to integrate HCL Domino® into your existing environment.

About this task

After planning is complete, you can begin to install and set up Domino® servers and the Domino® Administrator client and build the Domino® environment.

Procedure

Determine your company's server needs. Decide where to locate each server physically, taking into consideration local and wide-area networks and the function of each server.
Develop a hierarchical name scheme that includes organization and organizational unit names.
Decide whether you need more than one Domino® domain.
Understand how server name format affects network name-to-address resolution for servers. Ensure that the DNS records for your company are the correct type for the server names.
Determine which server services to enable.
Determine which certificate authority to use.
Install and set up the first Domino® server.
Install and set up the Domino® Administrator client on the administrator's machine. The Domino® Administrator client is available in the HCL Notes® Allclient install kit for the Windows™ platform only.
Complete network-related server setup.
If the Domino® server is offering Internet services, set up Internet site documents. There are some instances where Internet Site documents are required.
Specify administration preferences.
Create additional certifier IDs to support the hierarchical name scheme.
Set up recovery information for the certifier IDs.
Add the administrator's ID to the recovery information for the certifier IDs and then distribute the certifier IDs, as necessary, to other administrators.
Register additional servers.
If you did not choose to do so during first server setup, create a group in the Domino® Directory for all administrators, and give this group Manager access to all databases on the first server.
Install and set up additional servers.
Complete network-related server setup for each additional server.
Build the Domino® environment.