Home
Administering Volt
The following topics contain information for HCL Domino Volt 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 Volt.
Linux installation
The following topics describe how to install Link for use with Domino Volt.
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.
Link utility commands

Administering Volt
The following topics contain information for HCL Domino Volt admins.
- Controlling who creates HCL Volt applications
  To configure who can create and delete applications, you need to modify the Access Control List (ACL) for VoltBuilder.nsf.
- Volt configuration settings
  Volt 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 Volt is an add-on to the core HCL Domino server. Volt runs in the context of the Domino web server (HTTP process). Therefore, Volt is affected by the underlying Domino server configuration. This topic covers some of the core configuration settings that may affect Volt.
- Upgrading from prior releases
  Beginning with Volt 1.0.2, all Volt NSF files set the database property Don't Maintain Unread Marks as default, which should improve performance. NSF files created in prior versions of Volt are not changed.
- Adding a custom theme
- Volt Cleanup process
  Volt 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 Volt Cleanup Agent.
- Enabling basic authentication for HCL Volt 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 Volt server API URL paths and enable basic authentication.
- Securing your Volt 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 Volt.
    - 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 Volt.
      - 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.
        Link utility commands
      - Native installation
      - Docker installation
      - Troubleshooting
    - Configuring Link
    - Defining Link artifacts
      To use Link with Domino Volt, 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 Volt

Link utility commands

configure command

The configure command is required before using any other command. This command is used to specify the installation type, the OEM integration, and the user/group. You must specify the correct option for --integration at a minimum.

Table 1. Options
`--type <native\|docker>`	Specify the installation type. Default: native
`--integration <oem>`	Specify your integration.
`--license-file`	This option is intended for standalone customer use only. Do not use if you received HCL Link as an embedded solution.
`--user`	The user to install HCL Link to. This determines which user has ownership of the processes and directories. This must be an already existing user. Default: current user
`--group`	The group to install HCL Link as. This provides you with flexibility to share HCL Link directories with a group of admins. Default: current group

Note: You cannot change the integration type after you run install. If you notice a mistake after installation, extract the HCL Link package into a new directory and begin again.

install, uninstall, start, and stop commands

The behavior of the install, uninstall, start, and stop commands is similar.

All commands will act upon the default components if none are specified as options. You can specity the scope of each action by listing individual components.

Note: Embedded installations generally require all default components running for proper functionality. Do not use these options if you do not understand them fully.

Table 2. Options
`--runtime`	Runtime REST API
`--design-server`	Design Server

status command

The status command retrieves the status of each HCL Link component. The usage is similar between the native and docker installation types, though the possible states are different.

Table 3. Options
`--runtime`	Runtime REST API
`--design-server`	Design Server

Possible states

Native

Not Installed
Stopped
Running
Unknown

Docker

Not Installed
Created
Dead
Exited
Paused
Running
Restarting

logs command

The logs command prints the primary log of the chosen component. Because the log files may grow to a large size, you should funnel the output of this command into a tool like less for better navigation.

Table 4. Options
`--runtime-app`	Runtime REST API
`--design-server-app`	Design Server – Backend
`--design-server-client`	Design Server – UI