Home
Administering HCL Nomad
The following topics provide instructions on how to configure and manage HCL Nomad.
Troubleshooting (Nomad for web browsers)
This topic describles troubleshooting for administrators.

Administering HCL Nomad
The following topics provide instructions on how to 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 serves Nomad 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.
- 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.
- Configuring Nomad via notes.ini settings
  This topic describes how to configure notes.ini settings.
- 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.

Troubleshooting (Nomad for web browsers)

This topic describles troubleshooting for administrators.

Updating issues

After updating the Nomad files on the HTTP server to a newer version, if the clients are still running the older version and the update notification is not showing after multiple page refreshes, it may be due to the HTTP server refusing to serve files with older timestamps than those previously cached on the server.

This may occur when performing copy operations that modify the timestamp on files; when just unzipping files, the timestamps should be preserved, so updating Nomad server on Domino or Nomad for web browsers (Hosting the static web files on SafeLinx or Hosting the static web files on a Domino HTTP server) per the documented instructions should not encounter this issue.

To ensure that the new Nomad files have the latest timestamps, the administrator can run the following from the Nomad file directory:

Linux:
```
$ touch sw-bundle.js
```
Windows (CMD):
```
> copy /b sw-bundle.js +,,
```

After updating the timestamp, refresh Nomad in the web browser to continue the update process. After updating, confirm that Nomad is running the latest version by opening About HCL Nomad via the Help menu.