Home
Administering HCL Nomad
The following topics provide instructions on how to install, configure, and manage HCL Nomad.
Nomad server on Domino
The Nomad server on Domino services Nomad clients directly from your Domino server. It has been designed to simplify Nomad deployment.
Installation

Administering HCL Nomad
The following topics provide instructions on how to install, configure, and manage HCL Nomad.
- System architecture
  This topic describes the system architecture for HCL Nomad for web browsers, iOS, and Android.
- Nomad server on Domino
  The Nomad server on Domino services Nomad clients directly from your Domino server. It has been designed to simplify Nomad deployment.
  - Prerequisites and system requirements
  - Installation
  - Verify the configuration
  - Using the Nomad server behind a load balancer / reverse proxy
    You can use the Nomad server on Domino behind a reverse proxy.
  - Configuration options for the Nomad server on Domino
- SafeLinx as the Nomad server
  An HCL SafeLinx 1.2 or later server configured as a HCL Nomad server is required to handle communications with Nomad clients.
- HCL Nomad and panagenda MarvelClient
  The HCL Nomad management solution MarvelClient from panagenda is now provided with all installations of HCL Nomad on iOS, Android, and HCL Nomad for web browsers. panagenda MarvelClient allows administrators to manage HCL Nomad clients by defining their own settings.
- Managing HCL Nomad via an MDM provider (mobile)
  Starting with version 1.0.4 for HCL Nomad for iOS, and version 1.0.13 for HCL Nomad for Android, managed configuration via most common Mobile Device Management (MDM) providers is supported. All MDM providers are slightly different in how they implement managed configurations for applications.
- Configuring Nomad federated login
  When you configure Nomad federated login, HCL Nomad for web browser users are not prompted for their HCL Notes ID passwords when they set up Nomad. Instead, they are prompted only for credentials from a SAML identity provider (IdP) that is accessed through the Nomad server.
- Setting notes.ini values
  This topic describes how to configure notes.ini settings.
- Configuring notes.ini customizations
  This topic describes notes.ini settings used to customize startup and runtime behavior.
- Configuring application switcher (Nomad for web browsers)
  Application (app) switcher is an optional, configurable dropdown menu displayed on the left of HCL Nomad for web browsers' navigation bar. Each app switcher menu entry shows an application icon followed by the application’s name. Clicking on an app switcher menu entry navigates to the corresponding application address in a new browser tab.
- Shared usage (Nomad for web browsers)
  Nomad for web browsers administrators can force local user data to clear on shutdown. This option is only recommended when the usage pattern will be a new user each time Nomad is loaded or reloaded.
- Troubleshooting (Nomad for web browsers)
  This topic describles troubleshooting for administrators.

Installation

Before you begin

For downloading the application's static files for the Domino endpoint, see System requirements.

About this task

Pick one or more 12.0.2 or higher Domino servers to install on.
If you are upgrading Nomad server on Domino, please ensure that Nomad is not running (tell nomad quit) and prepare the /nomad-files sub-directory of the Domino program directory for the Nomad for web browsers update:
1. Backup the files and subdirectories of /nomad-files.
2. Delete /nomad-files.
Note:
- The default Domino program directory for Linux is /opt/hcl/domino/notes/latest/linux/.
- The default Domino program directory for Windows is C:\Program Files\HCL\Domino.
See System requirements to download the zip/tar file for the Nomad server on Domino endpoint and extract the file into the Domino program directory.

Note: If you would prefer not to unzip directly into the Domino program directory, you may unzip the file in a temporary location and then move or copy all the files, maintaining the subdirectory structure, into the Domino program directory.
If you are upgrading Nomad server on Domino, complete the following additional steps:
1. If you customized any files in /nomad-files/config/, copy those files from /nomad-files/config/ in the backup from step 2a.
2. (Optional): Delete the backup files and subdirectories from step 2a.
Start the Nomad task (load nomad). There should be no need to restart the Domino server itself.

Note: For Linux, extract as root. Otherwise, fix ownership and permissions of files after extraction.