Running analyses using QIAGEN CLC Workbenches and modules (commercial plugins) requires software licenses.
Two types of CLC software licenses are available:
1) Network licenses These are checked out from a central license manager when the CLC analysis software starts running, and are checked back in when that software is closed, allowing a single license to be used on different machines at different times. For modules, a network license is only checked out at the time the first tool delivered by a module is launched in a given Workbench session. Network licenses are required if the CLC software is installed on systems with more than 64 cores, or if the software will be accessed remotely. Network licenses are also used by CLC Grid Workers, when using a CLC Genomics Server with grid nodes.
Network licenses are downloaded to the CLC Network License Manager, which must be contactable by CLC Workbenches. The status of the network licenses, including how many licenses are available and how many are in use, can be monitored using tools supplied with the CLC Network License Manager software.
2) Static licenses A static license is downloaded to a specific machine, and supports running the software on that machine only. Static licenses can be used on systems with up to 64 cores. If the CLC analysis software is installed centrally on a machine, it can used by anyone logging into that machine directly. Remote connections are not supported when using a static license.
Rights and restrictions that apply to the software are described in the End User License Agreement.
Key considerations when choosing the type of license to purchase include:
How many people want to use the CLC software?
If there are just a few people using the CLC analysis software, they have their own machines where the software will be installed, and they are likely to be using the CLC software at the same time, then static licenses may be a good choice.
If there are more than a few people, or the few people using the software are likely to run the software at different times, then network licenses may be the better option. The number of network licenses for a particular product is the maximum number of instances of that product that can be used simultaneously.
So, for example, if 7 people are likely to use the software, but only 2 are likely to use it at the same time, 2 network licenses could be purchased, instead of 7 static licenses or instead of requiring people use a small number of designated work stations where static licenses have been installed..
Are machines being shared?
When there are several analysis work stations, but only some CLC software users, network licenses can be a good option. In this case, CLC Workbenches can be installed on any relevant machine and configured to contact the CLC Network License Manager.
From the software user’s perspective, the CLC software can be run on any machine it is installed on, as long as a network license for that product is available.
From the administrator’s perspective, all the Workbenches can be configured with the same licensing information, making for simple deployment/administration, and from the purchaser’s perspective, a small number of network licenses may suffice for a larger number of users, with the number of licenses depending on how many people want to use the CLC software simultaneously.
Do people want to use a CLC Workbench when they cannot connect to a CLC Network License Manager?
Both static and network licenses can be used offline. For network licenses, the CLC Workbench must be online to connect to the CLC Network License Manager to get a license, but then the license can be borrowed for a defined duration. By default, this can be for as little as an hour, up to a week. Licenses can be returned early if desired. Borrowing limits and borrowing restrictions can be configured by the CLC Network License Manager administrator. A common example where borrowing a license is useful is when a laptop with CLC analysis software installed on it is used for working at home for a few days without a VPN connection.
Are different people funding the purchase of licenses for CLC products?
Static licenses and network licenses offer different benefits in this situation. Static license are easy to conceptualize, but there is no scope for efficient use of the pool of licenses. Network licenses are an efficient and flexible option as access to particular licenses can be finely controlled. For example, licenses can be reserved for particular users or groups, or reserved for use on only particular machines based on host name or IP address (for individual computers or a subnet), and so on. Further details are in the user manual.
Do people need to access the CLC Workbench on a remote machine?
This type of access requires a network license.
Does the system the CLC Workbench is installed on have more than 64 cores?
This requires a network license.
