LICENSE_SERVER configuration parameter

The LICENSE_SERVER configuration parameter specifies the Informix instance about the FlexNet Server Device it needs to connect to obtain the necessary CPU license resources.

onconfig.std value
Not set.
A URL that points to the FlexNet Operations license server API, with <Device_ID> set to the Server Device name.<Device_ID>/ request

takes effect
On starting the instance, the FlexNet server indicated is queried to determine if sufficient licenses are available.


The HCL Informix Server instance must obtain sufficient license resources to start up all the CPU VPs specified in the onconfig file. It will fail to start if the licenses are not available. Any subsequent dynamic change to the CPU VP configuration will require rechecking the license entitlement with the FlexNet license server. The Informix instance will disable CPU VPs if there are no available licenses.

Care should be taken with the VPCLASS and AUTO_TUNE parameters to ensure that the correct initial request for CPU resource is made, and that any CPU VPs dynamically added by the system have sufficient licenses and do not cause license starvation issues for other instances using the same license server device.

If there are possible issues with license allocation between multiple Informix instances, using the same FlexNet Server Device, then it is possible to tie the license allocations to specific instances using FlexNet’s Reservation Group feature.

License allocations are returned when the Informix instance is stopped. If an instance fails, and is unable to return the licenses, then the licenses will be re-allocated when the server is restarted. If it is not possible to restart the server after a failure, and the licenses need to be returned for use by another instance, then the onclean utility can be used to return the licenses.

A Local License server cannot be installed on a virtual machine. The Informix instance, acting as a Client Device, accesses the license server through HTTP to a nominated port number, the default being 7070. Control and monitoring of the LLS through the REST interface is accomplished through a separate HTTPS port.

Copyright© 2018 HCL Technologies Limited