Difference between revisions of "Wibu Dongles"
Chris Huxley (talk | contribs) |
Chris Huxley (talk | contribs) |
||
(13 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
=Introduction= | =Introduction= | ||
− | TUFLOW Products are licenced via Codemeter locks, available in three forms; WIBU USB-2 Dongles (Hardware lock), WIBU Software Licences (Software lock) and WIBU Cloud locks.<br> | + | TUFLOW Products are licenced via Wibu Codemeter locks, available in three forms; WIBU USB-2 Dongles (Hardware lock), WIBU Software Licences (Software lock) and WIBU Cloud locks.<br> |
* '''WIBU Hardware Lock''': WIBU hardware locks are physical dongles (USB-2) that contain TUFLOW licences. Licences are coded onto the dongle and can be moved between computers. WIBU hardware locks are recognised by the 2006-06-BD release onwards. | * '''WIBU Hardware Lock''': WIBU hardware locks are physical dongles (USB-2) that contain TUFLOW licences. Licences are coded onto the dongle and can be moved between computers. WIBU hardware locks are recognised by the 2006-06-BD release onwards. | ||
*'''WIBU Software Lock''': WIBU software locks are coded onto the computer's or server's motherboard, it cannot be transferred to a different host. WIBU software locks are recognised by the 2016-03-AF release onwards. | *'''WIBU Software Lock''': WIBU software locks are coded onto the computer's or server's motherboard, it cannot be transferred to a different host. WIBU software locks are recognised by the 2016-03-AF release onwards. | ||
* '''WIBU Cloud Licence''': WIBU cloud licences are hosting on the WIBU cloud server. An internet connection is required to access a cloud licence. WIBU Cloud licences are recognised by the 2016-03-AF release onwards.<br> | * '''WIBU Cloud Licence''': WIBU cloud licences are hosting on the WIBU cloud server. An internet connection is required to access a cloud licence. WIBU Cloud licences are recognised by the 2016-03-AF release onwards.<br> | ||
The following pages provide details how to install, update and manage TUFLOW licences using all of the above forms. | The following pages provide details how to install, update and manage TUFLOW licences using all of the above forms. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<br> | <br> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | = | + | =Installation of CodeMeter RunTime Kit= |
− | + | The first step when using a Wibu licence for TUFLOW modelling is to install CodeMeter User Runtime. It needs to be installed for all computers that will be running TUFLOW or configured as a network licence server. | |
− | |||
− | + | * <u>[[Installing_Wibu_CodeMeter_Windows|Installing Wibu CodeMeter Windows]]</u>. | |
− | + | * <u>[[Installing_Wibu_CodeMeter_Linux|Installing Wibu CodeMeter Linux]]</u>. | |
− | |||
− | *<u>[[ | ||
<br> | <br> | ||
− | =Updating= | + | =Updating a Licence= |
There are a number of reasons that the Wibu licence may need to be updated, for example: | There are a number of reasons that the Wibu licence may need to be updated, for example: | ||
− | * To add additional | + | * To add additional licences |
* To update to new support year | * To update to new support year | ||
* To add rental licences | * To add rental licences | ||
− | For each change to the dongle, it will be necessary to provide a licence update request file to the TUFLOW staff. | + | For each change to the dongle, it will be necessary to provide a licence update request file to the TUFLOW staff. The procedure is the same for local and network licences, the request will need to be generated from the computer which has the licence container (eg. USB-2 hardware lock, software lock). |
− | The procedure is the same for local and network licences, the request will need to be generated from the computer which has the | + | ==Request a Licence Update== |
− | ==Request a | + | The instructions for creating a licence request differ slightly depending on the licence container type and operating system. <br> |
− | The instructions for creating a licence request differ slightly depending | ||
'''Hardware Licence (USB)''' <br> | '''Hardware Licence (USB)''' <br> | ||
− | * <u>[[WIBU_Licence_Update_Request | Wibu licence update request for Windows (normal)]]</u> - Unless specified otherwise by the TUFLOW staff, this option is the correct one | + | * <u>[[WIBU_Licence_Update_Request | Wibu licence update request for Windows (normal)]]</u> - Unless specified otherwise by the TUFLOW staff, this option is the correct one for a USB-2 hardware lock. |
* <u>[[WIBU_Licence_Update_Request_Uncoded | Wibu licence update request for Windows (uncoded or blank dongle)]]</u> - If you have been provided with a blank dongle or are using a non BMT dongle the TUFLOW producer code needs to be added when requesting the licence update.<br> | * <u>[[WIBU_Licence_Update_Request_Uncoded | Wibu licence update request for Windows (uncoded or blank dongle)]]</u> - If you have been provided with a blank dongle or are using a non BMT dongle the TUFLOW producer code needs to be added when requesting the licence update.<br> | ||
* <u>[[WIBU_Licence_for_Linux | Wibu licence update request for Linux]]</u> | * <u>[[WIBU_Licence_for_Linux | Wibu licence update request for Linux]]</u> | ||
Line 63: | Line 33: | ||
* Contact <u>sales@tuflow.com</u>. | * Contact <u>sales@tuflow.com</u>. | ||
− | ==Import a | + | ==Import a Licence Update== |
− | Once a licence update has been created, an update file will be | + | Once a licence update has been created, an update file will be provided to you via email. This update file will have the extension '''.WibuCmRaU'''. When an update is applied, this modifies the contents of the licence container (eg. USB-2 hardware lock, software lock), it does not need to be applied on each computer that will be used for TUFLOW modelling!<br><br> |
'''Hardware Licence (USB)''' | '''Hardware Licence (USB)''' | ||
* <u>[[WIBU_Licence_Update_Import | Importing a Wibu licence update for Windows]]</u> | * <u>[[WIBU_Licence_Update_Import | Importing a Wibu licence update for Windows]]</u> | ||
* <u>[[WIBU_Licence_for_Linux | Importing a Wibu licence update request for Linux]]</u> | * <u>[[WIBU_Licence_for_Linux | Importing a Wibu licence update request for Linux]]</u> | ||
− | |||
'''Software Licence (File)''' | '''Software Licence (File)''' | ||
* <u>[[WIBU_Licence_Update_Softlock_Import |Importing a Wibu licence update for Windows]]</u><br> | * <u>[[WIBU_Licence_Update_Softlock_Import |Importing a Wibu licence update for Windows]]</u><br> | ||
'''Cloud Licence''' | '''Cloud Licence''' | ||
− | * <u>[[WIBU_Cloud_Licence_Import | Importing a WIBU Cloud Licence]]</u>. | + | * <u>[[WIBU_Cloud_Licence_Import | Importing a WIBU Cloud Licence]]</u> |
+ | <br> | ||
+ | |||
+ | =Configuring Licence= | ||
+ | ==Configuring Network Server== | ||
+ | If the TUFLOW licence is a network licence, the computer hosting the dongle will need to be configured as a TUFLOW server. This is required even if the simulations are to be performed on the server. Instructions for configuring the network licence are detailed in the following page:<br> | ||
+ | *<u>[[WIBU_Configure_Network_Server| WIBU Configure Network Server]]</u> | ||
+ | |||
+ | ==Configuring Access to Network Licence== | ||
+ | To access TUFLOW licences on a remote network server, the CodeMeter runtime kit needs to be installed on the client machine. Once installed, CodeMeter needs to be configured to use the network licence. | ||
+ | Instructions for configuring the network licence are detailed in the following page:<br> | ||
+ | *<u>[[WIBU_Configure_Network_Client| WIBU Configure Network Client]]</u> | ||
<br> | <br> | ||
Line 84: | Line 64: | ||
==Diagnostics== | ==Diagnostics== | ||
===cmDust=== | ===cmDust=== | ||
− | When the CodeMeter | + | When the CodeMeter Runtime Kit is installed a diagnostics utility call '''cmDust''' is also installed. The following link provides instructions how to create a diagnostics file. This file may be request by <u>support@tuflow.com</u> when solutions to licensing issues are being investigated: |
* <u>[[WIBU_create_cmDust | Create CM Dust Diagnostics File]]</u> | * <u>[[WIBU_create_cmDust | Create CM Dust Diagnostics File]]</u> | ||
===Enabling Logging=== | ===Enabling Logging=== | ||
− | Codemeter allows you to write extended log files to | + | Codemeter allows you to write extended log files to your local drive. The following link provides instructions how to enable this feature: |
− | * <u>[[Codemeter_Enable_Logging | Enable Codemeter Logging]]</u> | + | * <u>[[Codemeter_Enable_Logging |Enable Codemeter Logging]]</u> |
=== Enabling Network Server License Monitoring=== | === Enabling Network Server License Monitoring=== | ||
− | Codemeter allows you to conduct real-time licence network monitoring. | + | Codemeter allows you to conduct real-time licence network monitoring. The following link provides instructions how to enable this feature: |
* <u>[[Network_Server_License_Monitoring | Network License Monitoring]]</u> | * <u>[[Network_Server_License_Monitoring | Network License Monitoring]]</u> | ||
Latest revision as of 11:40, 9 December 2024
Introduction
TUFLOW Products are licenced via Wibu Codemeter locks, available in three forms; WIBU USB-2 Dongles (Hardware lock), WIBU Software Licences (Software lock) and WIBU Cloud locks.
- WIBU Hardware Lock: WIBU hardware locks are physical dongles (USB-2) that contain TUFLOW licences. Licences are coded onto the dongle and can be moved between computers. WIBU hardware locks are recognised by the 2006-06-BD release onwards.
- WIBU Software Lock: WIBU software locks are coded onto the computer's or server's motherboard, it cannot be transferred to a different host. WIBU software locks are recognised by the 2016-03-AF release onwards.
- WIBU Cloud Licence: WIBU cloud licences are hosting on the WIBU cloud server. An internet connection is required to access a cloud licence. WIBU Cloud licences are recognised by the 2016-03-AF release onwards.
The following pages provide details how to install, update and manage TUFLOW licences using all of the above forms.
Installation of CodeMeter RunTime Kit
The first step when using a Wibu licence for TUFLOW modelling is to install CodeMeter User Runtime. It needs to be installed for all computers that will be running TUFLOW or configured as a network licence server.
Updating a Licence
There are a number of reasons that the Wibu licence may need to be updated, for example:
- To add additional licences
- To update to new support year
- To add rental licences
For each change to the dongle, it will be necessary to provide a licence update request file to the TUFLOW staff. The procedure is the same for local and network licences, the request will need to be generated from the computer which has the licence container (eg. USB-2 hardware lock, software lock).
Request a Licence Update
The instructions for creating a licence request differ slightly depending on the licence container type and operating system.
Hardware Licence (USB)
- Wibu licence update request for Windows (normal) - Unless specified otherwise by the TUFLOW staff, this option is the correct one for a USB-2 hardware lock.
- Wibu licence update request for Windows (uncoded or blank dongle) - If you have been provided with a blank dongle or are using a non BMT dongle the TUFLOW producer code needs to be added when requesting the licence update.
- Wibu licence update request for Linux
Software Licence (File)
After creating the licence update request, please email the created file (.WibuCmRaC) to sales@tuflow.com.
Cloud Licence
- Contact sales@tuflow.com.
Import a Licence Update
Once a licence update has been created, an update file will be provided to you via email. This update file will have the extension .WibuCmRaU. When an update is applied, this modifies the contents of the licence container (eg. USB-2 hardware lock, software lock), it does not need to be applied on each computer that will be used for TUFLOW modelling!
Hardware Licence (USB)
Software Licence (File)
Cloud Licence
Configuring Licence
Configuring Network Server
If the TUFLOW licence is a network licence, the computer hosting the dongle will need to be configured as a TUFLOW server. This is required even if the simulations are to be performed on the server. Instructions for configuring the network licence are detailed in the following page:
Configuring Access to Network Licence
To access TUFLOW licences on a remote network server, the CodeMeter runtime kit needs to be installed on the client machine. Once installed, CodeMeter needs to be configured to use the network licence.
Instructions for configuring the network licence are detailed in the following page:
Troubleshooting
- Hardware (USB) Dongle Not Working Correctly
- Network Connectivity Issue
- Network Server Issue
- Unable to Remove Licence Container
- Unable to Connect to Cloud Licence
Diagnostics
cmDust
When the CodeMeter Runtime Kit is installed a diagnostics utility call cmDust is also installed. The following link provides instructions how to create a diagnostics file. This file may be request by support@tuflow.com when solutions to licensing issues are being investigated:
Enabling Logging
Codemeter allows you to write extended log files to your local drive. The following link provides instructions how to enable this feature:
Enabling Network Server License Monitoring
Codemeter allows you to conduct real-time licence network monitoring. The following link provides instructions how to enable this feature:
Up |
---|
Back to Wiki Main Page |