WIBU Licence for Linux - Revision history

Jaap.vandervelde: fix mixed RHEL / Debian syntax

2026-03-27T01:31:26Z

fix mixed RHEL / Debian syntax

← Older revision		Revision as of 11:31, 27 March 2026
Line 1:		Line 1:
	For the process of requesting a Wibu-Systems Software License for a ''Windows'' licence host, please refer to [[WIBU Licence Update Request\|Wibu Software Licence Update Request]]. This article describes the process of setting up a software licence container and installing licence updates from a <i>Linux</i> command line interface, like one you would access on an SSH console. It applies to both Local and Network software licences, not cloud-based licences.		For the process of requesting a Wibu-Systems Software License for a ''Windows'' licence host, please refer to [[WIBU Licence Update Request\|Wibu Software Licence Update Request]]. This article describes the process of setting up a software licence container and installing licence updates from a <i>Linux</i> command line interface, like one you would access on an SSH console. It applies to both Local and Network software licences, not cloud-based licences.

	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 [https://www.wibu.com/support/user/user-software.html CodeMeter Runtime (download)] for your Linux host and CodeMeter is running as a service. If you are uncertain, you can run <pre>systemctl \| grep codemeter</pre> and you should see both `codemeter.service` and `codemeter-webadmin.service` as `running` or `exited`. For the CodeMeter service, you can also check <pre>~~/etc/init.d/codemeter~~ status</pre> which should report "CodeMeter Server is running.". By default, your CodeMeter Control Center web application would be hosted on <font color="#3366CC">http://<your hostname>:22352/</font> or <font color="#3366CC">https://<your hostname>:22353/</font> and accessible from <font color="#3366CC">http://<your hostname>:22350/</font>.		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 [https://www.wibu.com/support/user/user-software.html CodeMeter Runtime (download)] for your Linux host and CodeMeter is running as a service. If you are uncertain, you can run <pre>systemctl \| grep codemeter</pre> and you should see both `codemeter.service` and `codemeter-webadmin.service` as `running` or `exited`. For the CodeMeter service, you can also check <pre>systemctl status codemeter.service</pre> which should report CodeMeter Server as running. By default, your CodeMeter Control Center web application would be hosted on <font color="#3366CC">http://<your hostname>:22352/</font> or <font color="#3366CC">https://<your hostname>:22353/</font> and accessible from <font color="#3366CC">http://<your hostname>:22350/</font>.

	For a basic setup of CodeMeter on Linux, refer to [[Installing_Wibu_CodeMeter_Linux \| Installing Wibu CodeMeter on Linux]].		For a basic setup of CodeMeter on Linux, refer to [[Installing_Wibu_CodeMeter_Linux \| Installing Wibu CodeMeter on Linux]].
Line 57:		Line 57:

	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:		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:
	<pre>sudo systemctl restart codemeter.service~~</pre> or <pre>sudo /etc/init.d/codemeter restart~~</pre>		<pre>sudo systemctl restart codemeter.service</pre>

	==Using the installed licenses==		==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 <u>[[WIBU_Configure_Network_Server\|Wibu Configure Network Server]]</u> and <u>[[WIBU_Configure_Network_Client\|Wibu_Configure Network Client]]</u> to learn how to connect to it.		If you are running a model on another machine and have installed the license on a remote license host, refer to <u>[[WIBU_Configure_Network_Server\|Wibu Configure Network Server]]</u> and <u>[[WIBU_Configure_Network_Client\|Wibu_Configure Network Client]]</u> to learn how to connect to it.

Jaap.vandervelde: Reviewed, corrected errors on licence types, aligned with other wiki

2026-03-27T01:13:20Z

Reviewed, corrected errors on licence types, aligned with other wiki

← Older revision		Revision as of 11:13, 27 March 2026
Line 1:		Line 1:
	This article describes the process of setting up a ~~licence container (~~software licence ~~only)~~ and installing licence updates ~~(network and software licences)~~ from a <i>Linux</i> command line interface, like you would access on an SSH console.		For the process of requesting a Wibu-Systems Software License for a ''Windows'' licence host, please refer to [[WIBU Licence Update Request\|Wibu Software Licence Update Request]]. This article describes the process of setting up a software licence container and installing licence updates from a <i>Linux</i> command line interface, like one you would access on an SSH console. It applies to both Local and Network software licences, not cloud-based licences.

	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 [https://www.wibu.com/support/user/user-software.html CodeMeter Runtime (download)] for your Linux host and CodeMeter is running as a service. If you are uncertain, you can run <pre>systemctl \| grep codemeter</pre> and you should see both `codemeter.service` and `codemeter-webadmin.service` as `running` or `exited`. For the CodeMeter service, you can also check <pre>/etc/init.d/codemeter status</pre> which should report "CodeMeter Server is running.". By default, your CodeMeter Control Center web application would be hosted on [http://~~localhost~~:~~22350~~/ http://<your hostname>:22350/].		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 [https://www.wibu.com/support/user/user-software.html CodeMeter Runtime (download)] for your Linux host and CodeMeter is running as a service. If you are uncertain, you can run <pre>systemctl \| grep codemeter</pre> and you should see both `codemeter.service` and `codemeter-webadmin.service` as `running` or `exited`. For the CodeMeter service, you can also check <pre>/etc/init.d/codemeter status</pre> which should report "CodeMeter Server is running.". By default, your CodeMeter Control Center web application would be hosted on <font color="#3366CC">http://<your hostname>:22352/</font> or <font color="#3366CC">https://<your hostname>:22353/</font> and accessible from <font color="#3366CC">http://<your hostname>:22350/</font>.

	For a basic setup of CodeMeter on Linux, refer to [[Installing_Wibu_CodeMeter_Linux \| Installing Wibu CodeMeter on Linux]].		For a basic setup of CodeMeter on Linux, refer to [[Installing_Wibu_CodeMeter_Linux \| 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).		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 licence container ~~(software licence only)~~==		== Setting up a new software licence container ==

	Email <u>[mailto:sales@tuflow.com sales@tuflow.com]</u> to request a software licence. You will be sent an empty licence container file (*.WibuCmLif).		Email <u>[mailto:sales@tuflow.com sales@tuflow.com]</u> to request a software licence. You will be sent an empty licence container file (*.WibuCmLif).
Line 33:		Line 33:
	<pre>cmu --list</pre>		<pre>cmu --list</pre>

	==Updating licences ~~(network~~ ~~and~~ ~~software~~ ~~licences)~~==		== Updating licences in an existing licence container ==

	Once you have an existing licence container, either ~~from~~ ~~a plugged in~~ network ~~dongle~~ or ~~imported~~ ~~software~~ ~~container,~~ ~~you~~ ~~will~~ ~~need~~ to ~~create~~ a licence update request:		Once you have an existing licence container for either local or network licences, you can update it with licences by first creating a licence update request.
	* Network licence:
	<pre>cmu --context 101139 --serial x-xxxxxxx --file x-xxxxxxx.WibuCmRaC</pre>
	* Software licence:
	<pre>cmu --context 6000224 --serial xxx-xxxxxxxxxx --file xxx-xxxxxxxxxx.WibuCmRaC</pre>

			For hardware-based licences, on a dongle:<pre>cmu --context 101139 --serial x-xxxxxxx --file x-xxxxxxx.WibuCmRaC</pre>For software-based licences:<pre>cmu --context 6000224 --serial xxx-xxxxxxxxxx --file xxx-xxxxxxxxxx.WibuCmRaC</pre>Where "xxx-xxxxxxxxxx" / "x-xxxxxxxxxx" is the serial number of your licence container. E-mail the created licence request file (.WibuCmRaC) file to [mailto:sales@tuflow.com sales@tuflow.com].
	Where "x-xxxxxxx" or "xxx-xxxxxxxxxx" is the serial number of your licence container.

		⚫	Once your licence request is processed, you will receive a licence update file (.WibuCmRaU) in return, which you can install with
	E-mail the created licence request file (.WibuCmRaC) file to <u>[mailto:sales@tuflow.com sales@tuflow.com]</u>.
		⚫	<pre>cmu --import --file <serial>.WibuCmRaU</pre>

		⚫	Which should result in something like (this example for a software-based licence):
⚫	Once your licence request is processed, you will receive a licence update file (.WibuCmRaU) in return, which you can install with:
	* Network licence:
⚫	<pre>cmu --import --file ~~x-xxxxxxx~~.WibuCmRaU</pre>
	* Software licence:
	<pre>cmu --import --file xxx-xxxxxxxxxx.WibuCmRaU</pre>
⚫	Which should result in something like:
	<pre>cmu - CodeMeter Universal Support Tool.		<pre>cmu - CodeMeter Universal Support Tool.
	Version 6.60a of 2018-Feb-26 (Build 2878) for Linux		Version 6.60a of 2018-Feb-26 (Build 2878) for Linux

Chris Huxley: /* Using the installed licenses */

2026-01-09T00:39:27Z

Using the installed licenses

← Older revision		Revision as of 10:39, 9 January 2026
Line 75:		Line 75:
	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: <pre>WIBU Firm Code Search Order == 6000224 101139</pre> 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 <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>.		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: <pre>WIBU Firm Code Search Order == 6000224 101139</pre> 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 <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>.
	<br>		<br>
	{{Tips Navigation
	\|uplink=[[Wibu_Dongles\| Return to WIBU Licensing Main Page]]
	}}

Chris Huxley: /* Using the installed licenses */

2024-11-29T16:31:53Z

Using the installed licenses

← Older revision		Revision as of 02:31, 30 November 2024
Line 69:		Line 69:

	==Using the installed licenses==		==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 <u>[[WIBU_Configure_Network_Server\|Wibu Configure Network Server]]</u> and <u>[[~~WIBU_Configure_Network_Client_2016~~\|Wibu_Configure Network Client]]</u> to learn how to connect to it.		If you are running a model on another machine and have installed the license on a remote license host, refer to <u>[[WIBU_Configure_Network_Server\|Wibu Configure Network Server]]</u> and <u>[[WIBU_Configure_Network_Client\|Wibu_Configure Network Client]]</u> 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).		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).

Chris Huxley: /* Using the installed licenses */

2024-11-29T16:26:43Z

Using the installed licenses

← Older revision		Revision as of 02:26, 30 November 2024
Line 69:		Line 69:

	==Using the installed licenses==		==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 <u>[[~~WIBU_Configure_Network_Server_2016~~\|Wibu Configure Network Server]]</u> and <u>[[WIBU_Configure_Network_Client_2016\|Wibu_Configure Network Client]]</u> to learn how to connect to it.		If you are running a model on another machine and have installed the license on a remote license host, refer to <u>[[WIBU_Configure_Network_Server\|Wibu Configure Network Server]]</u> and <u>[[WIBU_Configure_Network_Client_2016\|Wibu_Configure Network Client]]</u> 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).		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).

Emilie Nielsen at 00:10, 23 September 2024

2024-09-23T00:10:03Z

← Older revision		Revision as of 10:10, 23 September 2024
Line 73:		Line 73:
	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).		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: <pre>WIBU Firm Code Search Order == 6000224 101139</pre> 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 <u>[https://~~www~~.tuflow.com/~~Tuflow%20Documentation.aspx~~ manual ~~can be downloaded~~ ~~here~~]</u>.		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: <pre>WIBU Firm Code Search Order == 6000224 101139</pre> 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 <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>.
	<br>		<br>
	{{Tips Navigation		{{Tips Navigation

Chris Huxley: /* Using the installed licenses */

2024-03-17T23:15:00Z

Using the installed licenses

← Older revision		Revision as of 09:15, 18 March 2024
Line 74:		Line 74:

	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: <pre>WIBU Firm Code Search Order == 6000224 101139</pre> 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 <u>[https://www.tuflow.com/Tuflow%20Documentation.aspx manual can be downloaded here]</u>.		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: <pre>WIBU Firm Code Search Order == 6000224 101139</pre> 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 <u>[https://www.tuflow.com/Tuflow%20Documentation.aspx manual can be downloaded here]</u>.
			<br>
			{{Tips Navigation
			\|uplink=[[Wibu_Dongles\| Return to WIBU Licensing Main Page]]
			}}

Emilie Nielsen at 23:40, 3 December 2023

2023-12-03T23:40:15Z

← Older revision		Revision as of 09:40, 4 December 2023
Line 9:		Line 9:
	==Setting up a new licence container (software licence only)==		==Setting up a new licence container (software licence only)==

	Email [mailto:sales@tuflow.com sales@tuflow.com] to request a software licence. You will be sent an empty licence container file (*.WibuCmLif).		Email <u>[mailto:sales@tuflow.com sales@tuflow.com]</u> to request a software licence. You will be sent an empty licence container file (*.WibuCmLif).

	Install the licence container file with:		Install the licence container file with:
Line 43:		Line 43:
	Where "x-xxxxxxx" or "xxx-xxxxxxxxxx" is the serial number of your licence container.		Where "x-xxxxxxx" or "xxx-xxxxxxxxxx" is the serial number of your licence container.

	E-mail the created licence request file (.WibuCmRaC) file to [mailto:sales@tuflow.com sales@tuflow.com].		E-mail the created licence request file (.WibuCmRaC) file to <u>[mailto:sales@tuflow.com sales@tuflow.com]</u>.

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

Pavlina Monhartova: Created page with "This article describes the process of setting up a licence container (software licence only) and installing licence updates (network and software licences) from a Linux..."

2021-09-01T05:38:07Z

Created page with "This article describes the process of setting up a licence container (software licence only) and installing licence updates (network and software licences) from a Linux..."

New page

This article describes the process of setting up a licence container (software licence only) and installing licence updates (network and software licences) 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 [https://www.wibu.com/support/user/user-software.html CodeMeter Runtime (download)] for your Linux host and CodeMeter is running as a service. If you are uncertain, you can run <pre>systemctl | grep codemeter</pre> and you should see both `codemeter.service` and `codemeter-webadmin.service` as `running` or `exited`. For the CodeMeter service, you can also check <pre>/etc/init.d/codemeter status</pre> which should report "CodeMeter Server is running.". By default, your CodeMeter Control Center web application would be hosted on [http://localhost:22350/ http://<your hostname>:22350/].

For a basic setup of CodeMeter on Linux, refer to [[Installing_Wibu_CodeMeter_Linux | 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 licence container (software licence only)==

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

Install the licence container file with:
<pre>cmu --import --file Universal_Firm_Code_CmActLicense_6000224.WibuCmLif</pre>
Which should result in something like:
<pre>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</pre>

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:
<pre>sudo systemctl restart codemeter.service</pre>

Make a note of the serial number displayed. You can list serial numbers of installed dongles and software licence containers with the command:
<pre>cmu --list</pre>

==Updating licences (network and software licences)==

Once you have an existing licence container, either from a plugged in network dongle or imported software container, you will need to create a licence update request:
* Network licence:
<pre>cmu --context 101139 --serial x-xxxxxxx --file x-xxxxxxx.WibuCmRaC</pre>
* Software licence:
<pre>cmu --context 6000224 --serial xxx-xxxxxxxxxx --file xxx-xxxxxxxxxx.WibuCmRaC</pre>

Where "x-xxxxxxx" or "xxx-xxxxxxxxxx" is the serial number of your licence container.

E-mail the created licence request file (.WibuCmRaC) file to [mailto:sales@tuflow.com sales@tuflow.com].

Once your licence request is processed, you will receive a licence update file (.WibuCmRaU) in return, which you can install with:
* Network licence:
<pre>cmu --import --file x-xxxxxxx.WibuCmRaU</pre>
* Software licence:
<pre>cmu --import --file xxx-xxxxxxxxxx.WibuCmRaU</pre>
Which should result in something like:
<pre>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</pre>

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:
<pre>sudo systemctl restart codemeter.service</pre> or <pre>sudo /etc/init.d/codemeter restart</pre>

==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|Wibu Configure Network Server]] and [[WIBU_Configure_Network_Client_2016|Wibu_Configure Network Client]] 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: <pre>WIBU Firm Code Search Order == 6000224 101139</pre> 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 [https://www.tuflow.com/Tuflow%20Documentation.aspx manual can be downloaded here].