Home
Administering HCL Nomad
The following topics provide instructions on how to install, configure, and manage HCL Nomad.
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.
Considerations

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.
- 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.
  - Using MarvelClient on Nomad clients
  - Configuring MarvelClient for Nomad
  - Disabling MarvelClient on Nomad clients
    MarvelClient on HCL Nomad can be disabled.
  - MarvelClient Web Migration
    A subset of panagenda MarvelClient functionality ships with Nomad for web browsers. One example of this is panagenda MarvelClient Nomad Web Migration. Additional capabilities can be purchased from panagenda.
  - MarvelClient Nomad Roaming
    A subset of panagenda MarvelClient functionality ships with all Nomad clients. One example of this is panagenda MarvelClient Nomad Roaming. Additional capabilities can be purchased from panagenda.
  - Configuring application restrictions on mobile Nomad clients
    This topic applies to HCL Nomad on iOS and Android.
  - Configuring application restrictions on Nomad for web browsers
  - Considerations
- 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.

Considerations

MarvelClient Connection and Location actions are not reflected after upgrading HCL Nomad application

Issue: When setting up the Nomad Mobile app, the settings in MarvelClient (such as creating a connection document to the personal address book) were automatically reflected. Since the update of the Nomad Mobile iOS app to 1.0.16.2021092923 and Nomad Mobile Android app to 1.0.22, there has been an issue where the MarvelClient settings are not being reflected. This behavior is the same for Nomad Web 1.0.1 in that Connection and Location actions are automatically disabled for Nomad Web.
Cause: This is due to an intentional change to MarvelClient. For more information, see Why don't my Location and Connection actions run on HCL Nomad? in the panagenda documentation.
Resolution: You can edit the Location and Connection actions in the Config Database of MarvelClient and manually enable one of the HCL Nomad platforms.
These actions are now disabled by default. If you want to re-enable, just need to edit the actions and specifically select the Nomad clients in order to re-enable.
Note: Some of the standard Notes client settings are not applicable to HCL Nomad, and they might cause problems with startup or connectivity.