Welcome
HCL Nomad for web browsers 1.0.x User Documentation
HCL Nomad is a client that allows users to work with Domino applications from their mobile devices and web browsers.
Using Nomad for web browsers
The following topics provide instructions on how to configure and use the browser for HCL Nomad for web browsers.
COM Helper
In order to have HCL Nomad for web browsers successfully process Component Object Model (COM) calls from agents and buttons, the Windows client machine needs to have HCL Nomad for web browsers COM Helper installed. COM is a Windows only feature, so the COM Helper only applies to web browsers running on a Windows machine.
Configuration
After the Nomad for web browsers COM Helper is installed, the default configuration of the browser extension should be sufficient in most cases, but there are some configuration options if necessary.

HCL Nomad for web browsers 1.0.x User Documentation
HCL Nomad is a client that allows users to work with Domino applications from their mobile devices and web browsers.
- What's new in HCL Nomad for web browsers
- System requirements
  Before you set up HCL Nomad for web browsers, check that your environment meets the following requirements.
- Using Nomad for web browsers
  The following topics provide instructions on how to configure and use the browser for HCL Nomad for web browsers.
  - Browser configuration
    This following topics provide information on how to set up Nomad for web browsers, which involves configuring a supported browser on your system and running Nomad via a Nomad server on Domino or SafeLinx URL.
  - Bookmarks
  - Shared usage
    You can preserve multiple users’ data when Nomad for web browsers is being accessed on a shared computer.
  - Notes links
  - Replication
  - Offline mode
    Offline mode allows users to continue working in local replicas without interruption if the connection is lost. This includes utilizing a local mail.box for sending mail while offline.
  - Restyle
    Domino Restyle updates an application's UI elements with a color-coordinated, cleaner look and feel. With Restyle, only UI elements are updated; no code is modified.
  - Designer
    You can use HCL Nomad for web browsers to design Notes databases.
  - File Storage
    Due to browser restrictions, Nomad for web browsers does not have access to the native operating system’s file system and instead uses the Origin Private File System (OPFS) to store files needed for ordinary operation. The OPFS is contained within the browser’s sandbox for the site and is not accessible from other sites nor the native operating system. Because the OPFS is in the browser storage, clearing the browser storage also clears the file system.
  - COM Helper
    In order to have HCL Nomad for web browsers successfully process Component Object Model (COM) calls from agents and buttons, the Windows client machine needs to have HCL Nomad for web browsers COM Helper installed. COM is a Windows only feature, so the COM Helper only applies to web browsers running on a Windows machine.
    - Install and Uninstall
      Follow these instructions to install and uninstall Nomad for web browsers COM Helper.
    - Configuration
      After the Nomad for web browsers COM Helper is installed, the default configuration of the browser extension should be sufficient in most cases, but there are some configuration options if necessary.
    - Examples
  - Sametime Integration
    Sametime integration is a feature included in Nomad for web browsers that enables two integration features with HCL Sametime:
- Troubleshooting and limitations
  The following topics provide information on limitations, troubleshooting tips, and instructions for reporting problems.
- Administering Nomad for web browsers

Configuration

After the Nomad for web browsers COM Helper is installed, the default configuration of the browser extension should be sufficient in most cases, but there are some configuration options if necessary.

Nomad in multiple domains

If you are using the same browser with different Nomad installations in different network domains, you need to modify the extension to add all the hosts to the allowed list. Make sure to only list hosts from secure domains that are under your control. Host entries should be just the host name (no https:// prefixes or trailing slashes). If your host is running on a non-standard port (not 443) you must include it as well. Example, mytrustedhost.domain2.com:9443

The whitelist.json file is created during installation in the installation directory and contains the list inside of a JSON object.

{ "whitelist": [ "mytrustedhost.domain1.com", "mytrustedhost.domain2.com:9443"] }.

Advanced deployment configuration

The COM Helper installer adds some registry entries to configure chrome to install the extension and properly use the native binary. These may conflict with (be overridden by) windows/chrome policies. You can modify your policies from these below settings, if necessary:

This registry entry causes Chrome to install the extension from the Chrome web store:

[HKLM/Software/Policies/Google/Chrome/ExtensionInstallForcelist]
"1352"="pkjkljikeelmnapkooflhchclfohcnmn"

This registry entry registers the native binary with Chrome by pointing to the manifest in the install directory that describes it.

[HKLM/Software/Google/Chrome/NativeMessagingHosts/com.hcl.nomad.webcom]
@="C:\\Program Files\\HCL\\HCL Nomad for web browsers COM helper\\manifest.json"

You may check what policies are active in Chrome by navigating a browser tab to:

chrome://policy

Some policies can cause conflicts so please review the following policies to ensure our extension (pkjkljikeelmnapkooflhchclfohcnmn) and native binary (com.hcl.nomad.webcom) are not blocked:

ExtensionInstallAllowlist
ExtensionInstallBlocklist
NativeMessagingAllowlist
NativeMessagingBlocklist