BASIS License Types (BLM)


This page contains information about the BASIS License Manager (BLM) associated with BASIS products up to version 21.0. The BLM has been superseded by the BASIS License Service (BLS) for BBj/BBx 22.0 and higher.

Other related resources worth viewing are Benefits of the ‘SoftwareAssetManagement’ Feature Line and Licensing Consumption.

Non-Virtual License Types


Perpetual licenses *are purchased for a single host ID and require a recent version of the BASIS License Manager (BLM). If you need to upgrade your BLM, BASIS provides a standalone BLM installation to facilitate upgrading the license manager without upgrading any other parts of the software suite.

The perpetual license can "self-heal," detecting and automatically re-registering when host IDs change due to operating system or hardware changes. Therefore, license resets are not required, and it is not necessary to contact your BASIS representative to purchase a license reset. BASIS includes a Software Asset Management (SAM) subscription, managed via the SoftwareAssetManagement license feature line. With the new perpetual licenses, you can easily renew or add a subscription to older licenses by contacting your BASIS sales representative.

Changing a host ID on a perpetual license does not invalidate the license or require a call to a BASIS sales representative to reset the license. You just need to restart the BLM and it will retrieve a new license with the new HostID in it. If you are moving to a new machine, you need to register for the license again with the serial number and authorization number to obtain a new license to ensure that the automatic registration will continue to function.

Additionally, the BASIS licensing software, FlexNet, includes a redundant license feature that allows one license with three hostids if used on up to three machines simultaneously. Licenses are dispensed as long as any two of the three are live. Redundant licenses are not eligible for virtualization.


Rental licenses* are purchased for twelve months and expire at the end of that period. BASIS includes Software Asset Management (SAM) subscription with rental licenses, managed via the SoftwareAssetManagement license feature line.


In the event your BLM server has crashed and you need to request a new license for a replacement machine, simply register for a new license with your existing Serial number and Authorization number. With our Perpetual Self Healing licenses there is no need for a license reset. If you do not have your Serial Number or Authorization number, there are two ways to retrieve this information:

  • Accessing your b-commerce account by clicking here.

  • Use the Emergency License web application to search for your information by clicking here.

Evaluation (Demo)

Evaluation licenses, for 5 days and 5 users, are available at no charge. Request this license type during the standard BBj/BLM install process. Call BASIS Sales for a custom demo license with an alternate duration and/or user count.

Developer Kit

Developer Kits* (DVK) are annual licenses for the cost of one year's SAM subscription, intended for development use and not for production environments.

*May be issued as a virtual license with a SAM subscription except for redundant licenses.

Virtual Machine Licensing

Cloud or virtual machine licensing facilitates running a license on virtualization software such as VMWare, XEN, or Amazon cloud, or as a single license if your host ID changes frequently. This license expires and renews automatically every 24 hours so that changing host IDs will not interrupt the production or development process.


Virtual licenses are available on new as well as old versions of BASIS products and require:

  • a BLM included in the BBj release, version 10.0 and higher
  • an active SAM subscription

How it Works

The BLM automatically re-registers for a new license each time the virtual BLM machine starts up with a different hostid. It also automatically re-registers a license that has 24 hours or less to expire, once per hour for the license life, until it successfully gets a new 24-hour license.

When the BLM attempts to start with a license that contains a different COMPOSITE= hostid, it attempts to re-register the license. If it re-registers successfully, the following "errors" will appear in the blm.log (normal behavior) and can be ignored:

        (lmgrd) BASIS exited with status 0 signal = 17
        (lmgrd) Since this is an unknown status, license server
        (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon

Simultaneously, the BLM writes an entry to the updatelic.log.

Live Migrations

At a live migration of a virtual machine, the guest is transferred from one physical host to another without a reboot. Users can continue to work with almost no interruption, and running programs will continue in their previous state on the new host. Currently, the BLM does support live migrations, as it does not automatically restart or update the license after a live migration of the guest.

Configure the License

In order for a virtual machine and perpetual licenses to work, the system that is running the BLM must be able to connect to via port 80 to update the license. If this is only possible via theuse of a proxy server, the BLM will need to be configured to use the proxy server. This can be done by placing a script called getlicense in the BLM directory.

If the BLM directory contains a file called getlicense, the BLM will execute it before trying to connect to directly. If the program in the getlicense file writes a license to standard output, the BLM will accept that as the new license. If you require the proxy server to supply a program or script, this will allow you to direct the download through the proxy server.  

Here is a sample getlicense script that duplicates the existing BLM behavior:


exec wget -q -O -$1

License Expiration

At time intervals determined by the expiration date of any feature line (license, SAM, etc.), the BLM looks at the BASIS database over an internet connection to verify that the product serial number and composite hostid are valid. When this information and an active SAM (Software Asset Management) subscription are verified, BASIS returns a new license to the BLM. If the license is unverified and has an inactive SAM subscription, BASIS issues no licenses and requires a reset fee or a new (renewed) SAM subscription for that serial number. SAM subscriptions are defined in the license by theSoftwareAssetManagementfeature line.

The license expiration process begins at midnight, local time, of the published date. For example, if the expiration date is Monday, April 15, the BLM starts checking the status of the license after 12:00 a.m. (local time) and attempts to update the license until 4 am. If it is unsuccessful, it will expire that evening at 11:59 p.m. The type of license determines its duration and expiration date.

Expiration date


> 20 days before [Exp date]

BLM does nothing until the license is 20 days from expiration, then it attempts to update the license.

 3-20 days before [Exp date]

BLM tries to update the license every twenty-four hours.

[Exp date]

Attempts to update the license between 12 am and 4 am local time. If the update is unsuccessful, the BLM retries every hour.

See Also

Benefits of the ‘SoftwareAssetManagement’ Feature Line

Licensing - Connection-based