Home
Administering Domino Leap
The following topics contain information for HCL Domino Leap admins.
HCL Link integration
HCL Link provides a platform for data and application integration.
HCL Link installation and administration
The following topics describe how to install and configure Link for use with Domino Leap.
Linux installation
The following topics describe how to install Link for use with Domino Leap.
Native installation

Administering Domino Leap
The following topics contain information for HCL Domino Leap admins.
- Controlling who creates HCL Domino Leap applications
  To configure who can create and delete applications, you need to modify the Access Control List (ACL) for VoltBuilder.nsf.
- Domino Leap configuration settings
  Domino Leap configuration settings are in VoltConfig.nsf in the volt folder of your Domino data directory (volt/VoltConfig.nsf). Use the Notes client or the Domino Administrator client to modify a configuration setting.
- Core Domino server configuration
  HCL Domino Leap is an add-on to the core HCL Domino server. Domino Leap runs in the context of the Domino web server (HTTP process). Therefore, Domino Leap is affected by the underlying Domino server configuration. This topic covers some of the core configuration settings that may affect Domino Leap.
- Upgrading from prior releases
  All Domino Leap NSF files set the database property Don't Maintain Unread Marks as default, which should improve performance. NSF files created in prior versions of Domino Leap are not changed.
- Adding a custom theme
- Domino Leap Cleanup process
  Domino Leap Cleanup primarily purges orphaned Builder attachments, orphaned application attachments, and old Preview databases. Prior to release 1.0.3, this process was done by the Domino Leap Cleanup Agent.
- Enabling basic authentication for HCL Domino Leap API requests
  If form-based authentication is enabled, you will see an HTML form for authentication instead of a pop-up window. This topic provides instructions on how to disable HTML form-based authentication for the HCL Domino Leap server API URL paths and enable basic authentication.
- Securing your Domino Leap deployment
- HCL Link integration
  HCL Link provides a platform for data and application integration.
  - HCL Link installation and administration
    The following topics describe how to install and configure Link for use with Domino Leap.
    - Windows installation
      The following topics describe how to install HCL Link on Windows.
    - Linux installation
      The following topics describe how to install Link for use with Domino Leap.
      - Link utility
        After extracting the HCL Link package, you can interact with the Link script to begin installation. Actual steps are provided in the Native and Docker installation sections.
      - Native installation
      - Docker installation
      - Troubleshooting
    - The Link configuration file (config.yaml)
      For a Link installation, configuration information is provided in the config.yaml file.
    - Configuring Link
    - Defining Link artifacts
      To use Link with Domino Leap, you must define connections to the resources you want to access, and then actions that define an operation that uses a connection.
  - Integrating Link with HCL Domino Leap
- Strict CSP
  HCL Domino Leap has a limited capability to restrict the rendering of Domino Leap Forms using a “Strict CSP” policy.
- Admin Application Dashboard
  The Admin Application Dashboard is a page that is available to members of the Admin or SuperAdmin groups.
- Integrating with HCL Volt MX Foundry
  HCL Domino Leap can now use the integration services defined in HCL Volt MX Foundry.

Native installation

Dependencies

bash (Bourne Again SHell)

ksh (KornShell)

libnsl

GNU sed

Prerequisites

You must have a MongoDB Server.

Configuration

Configure HCL Link before running any installation commands. If you choose not to, you might need to re-install for your updated configuration to take effect.

Configure the following files before installation (use ‘native’ post-fixed versions):

config.yaml

To re-configure after installation, update those files, and run the install command. This overwrites the configuration files in the install directory.

Several directories are specified in the configuration files. If the user or group you install into lacks R/W access to these directories, a system admin needs to create them and then transfer ownership.

If you are installing as non-root (recommended), change the client.inbound.port specified in config.yaml to a number above 1024 (default client port number is set to 4443). The standard Linux kernel prevents regular users from starting processes that bind to any port below 1024. Alternatively, you can use setcap to overcome this limitation:

Install Link before using setcap:

sudo setcap ‘cap_net_bind_service=+ep’ <link_package>/node-context/install/nodejs/bin/npm
sudo setcap ‘cap_net_bind_service=+ep’ <link_package>/node-context/install/nodejs/bin/node

Installation

Read the Link Utility documentation before following the installation steps. You may need to adjust commands according to your environment.

The commands listed in these steps are intended to demonstrate a quick-start scenario:

./Link configure --type native --integration oem
./Link install

Either start all components or continue to the Troubleshooting section for any errors:

./Link start