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® includes a Docker-compatible Red Hat Universal Base Image (UBI) of Domino that is part of your entitlement and available for download through the HCL Licensing Portal. HCL Domino is pre-installed on this image, allowing you to deploy Domino servers as containers with just a few commands.
Deploying a new Domino server on Docker
To deploy a new Domino server in a Docker container, complete the following steps.
Creating the volume to store the data directory
After you load the domino-docker tar archive to Docker, create a Docker volume. The Docker volume is a persistent location to hold the Domino data directory

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® includes a Docker-compatible Red Hat Universal Base Image (UBI) of Domino that is part of your entitlement and available for download through the HCL Licensing Portal. HCL Domino is pre-installed 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.
      - Types of Domino containers
        Use the docker run command to create a container that runs Domino. You can create the following types of Domino containers, based on the docker run arguments that you specify.
      - 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.
        Loading the domino-docker tar archive file to Docker
        The first step to deploy a new Domino server on Docker is loading the domino-docker tar archive file to Docker. This creates the image that's used to create containers.
        Creating the volume to store the data directory
        After you load the domino-docker tar archive to Docker, create a Docker volume. The Docker volume is a persistent location to hold the Domino data directory
        Creating a temporary container for remote server setup
        To deploy a new Domino server as a Docker container, first create a temporary container to complete remote Domino server setup.
        Creating a container for Domino
        After you have set up a new Domino server using a temporary container, create the container to run the Domino server.
      - Upgrading a containerized Domino server
        Upgrading a containerized Domino server is done differently than upgrading a non-containerized server.
      - Creating a container to run Domino processes with the server down
        If you need to run Domino processes such as fixup or updall when the server is down, create a specialized container.
      - Useful Docker commands
        Following are descriptions of some Docker commands that are useful for interacting with containers.
    - 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.
    - 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.
- 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.

Creating the volume to store the data directory

After you load the domino-docker tar archive to Docker, create a Docker volume. The Docker volume is a persistent location to hold the Domino data directory

About this task

Create a volume once for a given Domino server. It's easy to remove and recreate a Domino container, for example to upgrade to a new Domino version. When you do, the volume persists and the data directory is reused.

Procedure

Create the Docker volume for the data directory:

docker volume create <volume name>

For example, to create a volume named notesdata:

docker volume create notesdata

Note: If you use podman, the command is:

podman load --input Domino_1101_DockerImage.tgz