Home
Planning
Use this topic as an overview of planning task.
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.
Application security
Restrict access to Domino® applications to prevent unauthorized users from gaining access to information.

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 IBM® 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
  IBM® Domino® provides a range of directory service features.
- Planning a mail routing topology
  IBM® Domino® offers you considerable flexibility in configuring your mail system infrastructure, allowing you to use IBM 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 IBM® 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.
- Planning the NetBIOS network
  The IBM® Domino® network is compatible with NetBIOS, a set of IBM session-layer LAN services that has evolved into a standard interface that applications use to access transport-layer network protocols.
- Messaging overview
  The IBM® 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 IBM 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 IBM® 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.
  - Server security
    To secure Domino® servers, you allow and prevent user and server access.
  - Application security
    Restrict access to Domino® applications to prevent unauthorized users from gaining access to information.
  - Application design element security
    An application developer can further restrict access to design elements within an application using IBM® Domino® Designer.
  - Notes® and Domino® ID security
    To prevent unauthorized access to servers and applications, secure Notes® and Domino® IDs.
  - Workstation data security
    To prevent unauthorized access to user workstation information and applications, secure Notes® user computers.

Application security

Restrict access to Domino® applications to prevent unauthorized users from gaining access to information.

Table 1. Tasks for restricting access
Task	Use
Use the ACL to restrict application access.	Control Notes® and Internet/intranet user and Domino® server access to an application.
Enforce a consistent ACL.	Protects databases and templates on the server by forcing all changes to the ACL at a single location.
Encrypt applications	Prevent unauthorized users from accessing an application locally on a server or workstation.
Sign an application or template.	Identify the creator of an application or template. When a user accesses the application, the signature is checked to determined whether the action is allowed. For example, on a Domino® server the Agent Manager verifies the signature of an agent and checks whether the signer has the rights to perform the action. On a Notes® client, the signature is checked against the signer's rights in the workstation ECL.
Encrypt incoming and outgoing Notes® mail.	Ensure that only the intended recipient can read mail.
Electronically sign mail messages.	Verify that the person who sends the message is the author and that no one has tampered with the data.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.