License management
Learn important information about the licenses for your HCL Link product.
- Registering the host computer with the license server
  Before you can run a licensed feature, the computer where the feature is installed must register with the license server. Registering the computer’s host name enables HCL Link to obtain the licenses required to run licensed features on that computer.
- License feature names
  The license names of the HCL Link features display in the entitlement on the license server and in the messages that the runtime servers log. The feature names are also keywords of the dtxlicutil -view command.
- License allocation and persistence
  A license is required for each logical processor on the host computer where the licensed feature runs. The number of logical processors is the number of physical processors, or cores, multiplied by the number of virtual processors.
- License availability and usage
  An entitlement must have enough licenses available for the number of logical processors on the requesting host. If there are not enough available licenses for all logical processors, the request fails and the host does not acquire any licenses.
- License status on the host computer
  The dtxlicutil -local command displays the licenses that the host computer currently has. The available count and maximum count reflect the number of logical processors on the host computer, so the values for a single host are always the same.
- Releasing licenses
  Use the dtxlicutil -release command to release the licenses of all features from a host computer. The licenses return to the entitlement pool, where they are available for other hosts to acquire.
- Acquiring licenses
  After a host computer releases a license, you can request the license again by running the dtxlicutil -acquire command on the host...
- Troubleshooting license errors
  - License-message logging for runtime features
  - License-message logging for Pack features
- The dtxlicutil command
  The dtxlicutil command works with the licensed features of HCL Link HCL Link. Use it to register a computer with a license server, acquire or release licenses, and display details about license usage for an entitlement.

License-message logging for runtime features

The [Launcher] log settings in the install_dir/dtx.ini configuration file control the severity level of the license messages that are logged by the flow engine, Command Server, HCL Link API, and Packs features. See the release notes for details.

The flow engine logs license messages in the appropriate log files in the install_dir/logs directory:

CompoundSystem<date><time><hostname>.log, for all systems in a single process.
<unique_name><date><time><hostname>.log, for one or more systems that run in separate processes.

The Command Server logs license messages in the log file specified by the [Connections Manager] DebugName= setting in the dtx.ini configuration file. If the HCL Link API does not specify a callback, the API also logs license messages in the DebugName= file.

The license messages are:

DTXLN2155I: DTX License Info
DTXLN3114W: DTX License Warning
DTXLN4140E: DTX License ERROR

For example, HCL Link cannot obtain a Pack for Supply Chain license when the flow engine tries to run a map that has a Supply Chain schema in a card. The flow engine or CompoundSystem log file contains license messages like the following:


DTXLN2155I - Fri Feb 7 07:47:20 2018 - tid: 22212 inst: 0 - DTX License Info : Initializing HCL Link license library (.\mercpim.cpp:652) 
DTXLN2155I - Fri Feb 7 07:47:20 2018 - tid: 22212 inst: 0 - DTX License Info : Checking for license feature HIP_Cores (.\mercpim.cpp:679) 
DTXLN2155I - Fri Feb 7 07:47:24 2018 - tid: 22212 inst: 0 - DTX License Info : Checking for license feature HIPSC_Cores (.\mercpim.cpp:679) 
DTXLN4140E - Fri Feb 7 07:47:40 2018 - tid: 22212 inst: 0 - DTX License ERROR : License feature 'HIPSC_Cores' is not available for input card 1 (C:\mapdev.901\txenv\mercator\mercioex.c:563)