Release notes

Read the latest release specific information for HCL Link version


This release is a full installation of the product.

License requirements

HCL Link runtime features and Packs require a license to run. These features include:
  • HCL Link (Map Command Server, Flow Command Server, Flow Listeners and Link API)
  • HCL Link Pack for Healthcare
  • HCL Link Pack for Supply Chain EDI

HCL Link does not require a license to run maps or flows; however, you need a license to use the API that installs with Link. Registering with the license server is explained in this documentation.

Before you begin

HCL Software manages software licensing and downloads through the License and Delivery Portal. These release notes assume that you have ordered software and followed the instructions that you received to activate your entitlement and download the software from the Portal. You cannot use these release notes to configure and run HCL Link runtime features until you complete the following steps:

  1. Order software and receive the URL and login credentials for the License and Delivery Portal.
  2. Log in to the Portal.
  3. Create a User associated with your account.
  4. Create a Device to host the license server and record the server ID that is returned when the device is created.

    Important: The server ID uniquely identifies your company’s entitlement and should be kept secure.

  5. Map your entitlement to the license server Device.
  6. Download the software package:
    Link Component Download Package ID File Name
    Link components for Linux® platforms LNK_1.1.3_LNX lnkrt_1.1.3.0_linux_x64.tar.gz
    Link components for Windows® platforms LNK_1.1.3_WIN lnkrt_1.1.3.0_win64.exe

Registering the host with the license server

An HCL Link feature license comes from your company’s entitlement, which is a pool of licenses on the license server. Before you can run a licensed feature, the host computer where the feature is installed must register with the license server. Registering the host enables HCL Link to obtain the licenses required to run licensed features on that host.

After installation, run the dtxlicutil command to register the computer with either the cloud license server or a local license server, as described below:
  • On Windows systems, run the command from the installation directory (install_dir).
  • On Linux systems:
    • Run the . ./setup command from the installation directory before running the dtxlicutil command from /bin directory. After the command dtxlicutil is run, the dtxlic.ini file is generated in the config directory.

To register with the cloud license server, run:
dtxlicutil -type cls -serverurl server_url -serverid server_id

To register with the local license server, specify either the hostname and port or the IP address and port of the local license server. Also include "https://" when providing the hostname or IP address. For example, see below:

dtxlicutil -host https://hostname:port
dtxlicutil -host https://ip_addr:port

Logging license messages

To ensure that license messages are recorded in the log, verify that warning and error message logging is enabled in the install_dir/dtx.ini configuration file. (Note that warning and error message logging are enabled by default.) Optionally, you can also log informational license messages, but the informational messages of all processes that use the log settings are also logged, which significantly increases the log file size.

In the [Launcher] section of the dtx.ini file:

LogInfo=1 (optional)



When running the Map Command Server, license messages are logged in the file that you specify in the [Connections Manager] section of the install_dir/dtx.ini configuration file. License messages are also logged in this file when an application that invokes the Link API does not specify a callback.

In the [Connections Manager] section of the dtx.ini file, uncomment the DebugName= setting and specify a file name. For example:


For details about the logs, see the Licensing documentation.

When running the Flow Command Server, license messages are logged in the Flow Command Server log file and saved in the logs directory. Enable INFO level (--trace INFO) to see the Flow Command Server license informational messages.