WIBU Licence for Linux: Difference between revisions
Content deleted Content added
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 <i>Linux</i>..." |
Chris Huxley (talk | contribs) |
||
| (4 intermediate revisions by 2 users not shown) | |||
Line 9:
==Setting up a new 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).
Install the licence container file with:
Line 43:
Where "x-xxxxxxx" or "xxx-xxxxxxxxxx" is the serial number of your licence container.
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:
Line 69:
==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>[[
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
<br>
{{Tips Navigation
|uplink=[[Wibu_Dongles| Return to WIBU Licensing Main Page]]
}}
| |||