Home
Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
Installing and upgrading Domino® servers
Perform a new or upgrade install of one or many Domino® servers.
Preparing for installing and setting up Domino® servers
Installing an HCL Domino® server is the first part of deploying a server. The second part is using the Domino server setup program to configure the server.
Domino on Docker
HCL Domino® is available as a container image that can be used with current Docker or Podman runtimes. HCL Domino is preinstalled on this image, allowing you to deploy Domino servers as containers with just a few commands.

Installing
Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
- Installing and upgrading Domino® servers
  Perform a new or upgrade install of one or many Domino® servers.
  - Preparing for installing and setting up Domino® servers
    Installing an HCL Domino® server is the first part of deploying a server. The second part is using the Domino server setup program to configure the server.
    - Entering system commands
      Some of the procedures that follow include instructions for entering commands at the system command prompt.
    - Domino on Docker
      HCL Domino® is available as a container image that can be used with current Docker or Podman runtimes. HCL Domino is preinstalled on this image, allowing you to deploy Domino servers as containers with just a few commands.
      - Domino on Docker requirements
        Understand the requirements and current limitations for Domino on Docker.
      - Docker run command arguments
        To create containers for Domino, you use the the docker run command with the following arguments.
      - Creating a secrets file for a password-protected server ID
        If a Domino server ID is password-protected and you run the Domino container in detached mode where an administrator cannot input the password directly, create a secrets file to store the password. The Domino server reads the password from the secrets file.
      - Deploying a new Domino server on Docker
        To deploy a new Domino server in a Docker container, complete the following steps.
      - Upgrading a containerized Domino server
        Upgrading a containerized Domino server is very similar to upgrading a non-containerized server, except that instead of installing a new version, the existing container is stopped and removed, and the existing data volume is used to create a new container using an updated Domino container image. Starting the container the first time with a new image takes care of applying templates to the existing data volume.
      - Useful Docker commands
        Following are descriptions of some Docker commands that are useful for interacting with containers.
      - Running Domino-related commands inside the container
    - Domino® server installation
      The first step in deploying a Domino® server is installation, or copying the program files to the system's local drive.
    - Disabling concurrent I/O and direct I/O on Domino® servers on AIX®
      Concurrent I/O (CIO) and Direct I/O (DIO) are not supported with Domino® servers. CIO is a file system feature introduced in IBM® AIX® 5.2.0.10, also known as maintenance level 01, in the Enhanced Journaling File system (JFS2). This feature improves performance for relational databases.
    - Domino® server setup program
      The Domino® server setup program guides you through the choices you make to configure a Domino server. Setting up the first Domino server in a domain establishes a framework that consists of the Domino Directory, ID files, and documents. When you set up additional servers, you build upon this framework.
    - Using the Domino® server setup program
      The following procedures describe the ways you can use the server setup program.
    - One-touch Domino setup
      Use one-touch Domino setup to simplify setting up a server.
    - Understanding the Domino® server certification log
      The Domino® certification log records server certification and ID information.
    - Domino® server registration
      Before you install and set up additional servers, you must register them. In effect, registering a server adds the server to the system. The server registration process creates a Server document for the server in the Domino® Directory and creates a server ID. After registering and installing a server, you use the server setup program to obtain a copy of the Domino Directory for the new server and to set up the server to run particular services and tasks -- for example, the HTTP service, the Mail Router, and so on.
    - Optional tasks to perform after Domino® server setup
      You can perform addition tasks after server startup.
    - Starting and shutting down the Domino® server
      Start the Domino® server at the server console.
    - Starting Domino® as an application or a Windows™ service
      If you have installed Domino® as a Windows™ service, when you start the Domino server, you are prompted to specify whether to start Domino as an application or a Windows service.
    - Using instant messaging in the Domino® Directory
      The Domino® Directory is enabled for instant messaging, meaning that you can conduct an online chat directly from the Domino Directory.
    - Running the Domino-Portal integration wizard
      Use the Domino-Portal integration (DPI) wizard to configure an IBM® WebSphere® Portal server to work with your Domino-based infrastructure.
  - Uninstalling a Domino® server
    While it is not necessary to uninstall a Domino® server prior to upgrading to a new Domino release, you may want to uninstall a server.
- Downloading and distributing software using AutoUpdate
  AutoUpdate notifies you of the latest HCL Domino and Domino product family available on the Domino server, and allows you to download the software. You can also use it to distribute software to groups or selected Domino servers.
- Installing and upgrading Notes® clients
- Upgrading
  Use this documentation to upgrade the existing Domino® server and subsequently upgrade the Notes® client to a new release. You can also upgrade additional clients such as Domino Administrator and Domino Designer clients and additional features and plug-ins such as the embedded HCL Sametime® client.

Domino on Docker

HCL Domino® is available as a container image that can be used with current Docker or Podman runtimes. HCL Domino is preinstalled on this image, allowing you to deploy Domino servers as containers with just a few commands.

As of Domino 12.0.2, the container image is based on the HCL open source domino-container project.

This documentation provides information on common functionality. Other available features are documented by the HCL open source domino-container community.

Note: The image is available for download through the HCL Licensing Portal.

To get started, here are some container terms that are useful to know.

image A file that contains a built, executable version of an application. Images are uploaded to Docker and used to create and run containers.
container An isolated location on a Docker host that contains the executable software and files required to run an application. Containers exclude unnecessary files managed by the host operating system.
volume A location on Docker that stores data to be read or written by the application.While containers are easily deleted and recreated, volumes persist. The Domino data directory is stored in a volume and you can act on the corresponding Domino container without affecting the contents of the volume.
Docker daemon The Docker service that you interact with through the docker commands to create and manage containers. Also referred to as the Docker Engine.
Docker host The physical computer that runs the Docker daemon.
Podman is an alternative runtime, providing the same commands. Replace "docker" with "podman" for the commands issued.