Home
Administering HCL Nomad
The following topics provide instructions on how to install, configure, and manage HCL Nomad.
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.
Completing the prerequisites
Before you begin configuring the HCL Nomad server, complete the following prerequisites:
Hosting the Nomad for web browsers static web files
This topic only applies to Nomad for web browsers.
Hosting the static web files on a Domino HTTP server

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.
- 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.
  - Getting started with Nomad server wizard
  - Completing the prerequisites
    Before you begin configuring the HCL Nomad server, complete the following prerequisites:
    - Configuring a Domino LDAP server for Nomad
    - Hosting the Nomad for web browsers static web files
      This topic only applies to Nomad for web browsers.
      - Hosting the static web files on SafeLinx
        Before you configure the Nomad server you need to deploy the static files for the Nomad Web Application on the SafeLinx server.
      - Hosting the static web files on a Domino HTTP server
  - Collecting required information
  - Installing and setting up SafeLinx
  - Configuring the Nomad server
  - Logging in to verify the configuration
  - Configuring SafeLinx to accept LTPA cookies from other servers
    If there are other servers in the Nomad server network configured for single sign-on, you can configure SafeLinx to accept LTPA cookies from those servers.
- 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.
- 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.

Hosting the static web files on a Domino HTTP server

About this task

This task only applies if you are hosting the Nomad for web browser static application files on a Domino HTTP server which SafeLinx references.

Procedure

Identify the directory inside the Domino data directory that will contain the static web files that Domino HTTP utilizes (for example, inside /domino/html as /nomad). This directory will be used for initial installations as well as all updates.

Note: If the directory does not exist, create a new directory. The new directory needs to be under /domino/html, but the administrator can name that directory whatever they want.

Note: If the directory already exists, backup the files (optional) and then delete all of the files including all the subdirectories.
Unzip the static web files in the empty directory.
Configure Domino HTTP to serve the HTTP files with the HTTP headers (see Hosting the Nomad for web browsers static web files).

If you are using Internet Site Documents, the HTTP headers are specified via an HTTP response headers Web Site Rule. If you are not using Internet Site Documents, you may use the HTTPAdditionalRespHeader notes.ini.

Note: For more information, see Creating a Web Site Rule document.
Domino HTTP must specify the Content-Type for the .wasm files as application/wasm. Domino 11 and higher already includes this content-type definition, but earlier version of Domino will need this line added to the httpd.conf file:
```
AddType  .wasm     application/wasm                     # WebAssembly
```

SafeLinx

About this task

The configuration of SafeLinx to reference these Domino HTTP hosted files will be done later as part of SafeLinx configuration, but if HCL Nomad is already configured in SafeLinx, you need to update the SafeLinx configuration by completing the steps in VIA DOMINO HTTP SERVER in the topic Adding a Nomad server resource.