Tuflow

WIBU Licence for Linux: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
No edit summary
fix mixed RHEL / Debian syntax
 
(6 intermediate revisions by 3 users not shown)
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 licence container (software licence only)container and installing licence updates (network and software licences) 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/codemetersystemctl status codemeter.service</pre> which should report "CodeMeter Server isas running.". By default, your CodeMeter Control Center web application would be hosted on [<font color="#3366CC">http://localhost<your hostname>:2235022352/</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]].
 
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 (software licence only)==
 
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:
<pre>cmu --list</pre>
 
== Updating licences (networkin andan softwareexisting licence container licences)==
 
Once you have an existing licence container, for either fromlocal a plugged inor network donglelicences, oryou importedcan softwareupdate container,it youwith willlicences needby tofirst createcreating 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 x-xxxxxxx<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.
Version 6.60a of 2018-Feb-26 (Build 2878) for Linux
Line 66 ⟶ 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:
<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 <u>[[WIBU_Configure_Network_Server_2016WIBU_Configure_Network_Server|Wibu Configure Network Server]]</u> and <u>[[WIBU_Configure_Network_Client_2016WIBU_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).
 
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://wwwdocs.tuflow.com/Tuflow%20Documentation.aspx classic-hpc/manual/latest/ can be downloadedTUFLOW hereManual]</u>.
<br>
Retrieved from "https://wiki.tuflow.com/WIBU_Licence_for_Linux"