Welcome
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.
Prerequisites and system requirements

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 on Domino behind a reverse proxy / load balancer
    You can use the Nomad server on Domino behind a proxy functioning as a reverse proxy, load balancer, or both.
  - Configuration options for the Nomad server on Domino
  - Configure SAML authentication for Nomad server on Domino
    Create an IdP configuration document for Nomad server for Domino to participate in SAML authentication.
  - Configuring Nomad server on Domino with Domino as OIDC provider
- 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 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).
- 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.
- Configuring Sametime Integration (Nomad for web browsers)
- 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.

Prerequisites and system requirements

System requirements

Domino 12.0.2 or higher on Windows or Linux; if using Domino as the OIDC provider for OIDC login or Nomad federated login with OIDC, Domino 14.0.0 FP2 or higher on Windows or Linux.

Client requirements

Nomad for web browsers 1.0.5 or higher

Note: This only applies when changing Nomad for web browsers independently, as the Nomad server installation already includes a supported version of Nomad for web browsers.
Nomad for iOS 1.0.23 or higher
Nomad for Android 1.0.31 or higher

Hardware/Software/Memory requirements

See: Domino Requirements.

Set up Domino ID Vault

Make sure a Domino ID vault is configured on a Domino 12 or higher server; if Domino is going to be configured as the OIDC provider, Domino 14.0.0 FP2 or higher is required. Nomad user IDs will be stored in the vault. See the following topics in the Domino documentation:

Creating and configuring an ID vault
Viewing user IDs in a vault
If using Nomad federated login with SAML, see Using Security Assertion Markup Language (SAML) to configure federated-identity authentication.
If using Nomad federated login with OIDC, see Using OpenID Connect (OIDC) to configure federated-identity authentication

Decide on TLS certificates

If the Nomad clients will be talking directly to the Nomad server on Domino, acquire a trusted TLS certificate for the Nomad server on Domino. For more details, see Configuration options for the Nomad server on Domino.
Otherwise, whatever proxy the Nomad clients are talking to needs the trusted TLS certificate. See your proxy's documentation for further details.