WIBU Software Licence Linux

From TUFLOW FV Wiki
Jump to: navigation, search

For the process of requesting a Wibu-Systems Software License for a Windows licence host, please refer to Wibu Software Licence Update Request. This article describes the process of setting up a licence container and installing license updates from a Linux command line interface, like you would access on an SSH console.

The Linux commands used on this wiki should work on most modern Linux distributions, but were tested on CentOS and Debian. This article assumes you have downloaded and installed an appropriate version of the CodeMeter Runtime (download) for your Linux host and CodeMeter is running as a service. If you are uncertain, you can run
systemctl | grep codemeter
and you should see both `codemeter.service` and `codemeter-webadmin.service` as `running` or `exited`. For the CodeMeter service, you can also check
/etc/init.d/codemeter status
which should report "CodeMeter Server is running.". By default, your CodeMeter Control Center web application would be hosted on http://<your hostname>:22350/.

For a basic setup of CodeMeter on Linux, refer to Installing Wibu CodeMeter on Linux.

Software licences are an alternative option to hardware USB dongle licences. Please select the licence host carefully as a software based dongle will be bound to it when it is first imported. If over time you decide you want to move to another computer we will need to re-issue you with a new software licence (which will incur a small administration fee).

Setting up a new software licence container

Email sales@tuflow.com to request a software licence. You will be sent an empty licence container file (*.WibuCmLif).

Install the licence container file with:

cmu --import --file Universal_Firm_Code_CmActLicense_6000224.WibuCmLif

Which should result in something like:

cmu - CodeMeter Universal Support Tool.
Version 6.60a of 2018-Feb-26 (Build 2878) for Linux
Copyright (C) 2007-2018 by WIBU-SYSTEMS AG. All rights reserved.

The file contains 1 Update:
  CmActLtLicense binding information: FirmCode 6000224

Execute Update ...
The file contains 1 Update:
  CmActLtLicense update: Serial number xxx-xxxxxxxxxx, FirmCode 6000224.
   --> successful
1 successful update done

After installing the licence container file, the CodeMeter WebAdmin interface may report an error if you try to check the new container (e.g. 'Error 407: Unknown error'). This can be resolved by restarting the CodeMeter service after installing the licence container:

sudo systemctl restart codemeter.service

Make a note of the serial number displayed. You can list serial numbers of installed dongles and software licence containers with the command:

cmu --list

Updating licences in an existing licence container

Once you have an existing licence container, you can update it with licences by first creating a licence update request:

cmu --context 6000224 --serial xxx-xxxxxxxxxx --file xxx-xxxxxxxxxx.WibuCmRaC

Where "xxx-xxxxxxxxxx" is the serial number of your licence container. E-mail the created licence request file (.WibuCmRaC) file to sales@tuflow.com.

Once your licence request is processed, you will receive a licence update file (.WibuCmRaU) in return, which you can install with:

cmu --import --file xxx-xxxxxxxxxx.WibuCmRaU

Which should result in something like:

cmu - CodeMeter Universal Support Tool.
Version 6.60a of 2018-Feb-26 (Build 2878) for Linux
Copyright (C) 2007-2018 by WIBU-SYSTEMS AG. All rights reserved.

The file contains 1 Updates:
  CmActLtLicense binding information: FirmCode 6000224
  CmDongle update for 130-3796453031 (FirmCode 6000224).

Execute Update ...
The file contains 1 Updates:
  CmActLtLicense update: Serial number xxx-xxxxxxxxxx, FirmCode 6000224.
   --> successful
1 successful update done

Once your licence update has been imported, you should see your installed licences in the CodeMeter WebAdmin. If they fail to show up, restart the CodeMeter Service:

sudo systemctl restart codemeter.service
or
sudo /etc/init.d/codemeter restart

Using the installed licenses

If you are running a model on another machine and have installed the license on a remote license host, refer to Wibu Configure Network Server 2016 and Wibu_Configure Network Client 2016 to learn how to connect to it.

If the software license container is the only license container (i.e. you have no dongle installed), you can test using the installed license by simply starting a model run that requires it (i.e. some run other than a benchmark or tutorial model).

However, if you have both a dongle and software license container installed, you can ensure TUFLOW prefers the software license by creating a license control file (.lcf) for your model, with the line:
WIBU Firm Code Search Order == 6000224 101139
This ensures that TUFLOW will prefer a software license container (6000224) over a dongle license container (101139) to obtain a license. You can learn more about where such a file can be placed and what the followed logic for obtaining a license is in the TUFLOW manual, section 11.5.1.1 Protocols for Accessing Dongles; the manual can be downloaded here.