Search TipsLocal License Syntax
Node-Locked License Syntax
A node-locked or uncounted RLM license looks like this:
LICENSE foundry katana_i 2012.1006 permanent uncounted hostid=000ea641d7a1 share=h start=6-oct-2012 issued=6-oct-2012 _ck=fbf430af8c sig="60PG4515BFTJCYAXSYJ6GTUJ3B9NRRGF3VUUKD022M0BXU48SSESUGSAFJ8BAD5BN883526ETKQ0"
Node-locked RLM licenses are broken down into 11 parts:
• LICENSE - indicates the start of an RLM license feature.
• foundry - the vendor name. All licenses from the Foundry must contain the vendor name foundry.
• katana_i - the product to be licensed. In this example, it’s a Katana interactive license. A background render license would be katana_r.
• 2012.1006 - the maintenance date. All Katana releases built before this date will run until the license timeout. All releases built after this date will not run.
• For non-maintenance products, this is often just the version of the product, for example 3.0.
• permanent - this is a permanent license. If this field were a date 5-jul-2012, it would be a temporary license with that expiry date.
• uncounted - this is a node-locked license. Floating licenses have a number in place of the uncounted tag.
• hostid - also known as the System ID, this is the ethernet (mac) address of the machine to be licensed.
• share - this indicates how multiple checkouts from the same client machine are treated. share=h indicates licenses are shared by the same host.
• start=6-oct-2012 - the date when the license starts. This date may be in the future.
• issued - the day the license was made, which may differ from the license start date.
• ck and sig - the encrypted license key. It represents a unique hash of the information in the license and is used to validate the license.
Floating License Syntax
A floating or counted RLM license looks like this:
HOST <server_name> <server host id> <port>
ISV foundry <options file> <port>
LICENSE foundry mari_i 2012.1006 permanent 10 share=h start=6-oct-2012 issued=6-oct-2012 _ck=fb063057fd sig="60PG451E0VM5S81E5EWRYM8E82CMKYR6SSB93P822M0AT1UU7FWA85M9P34UKXK4HMD7ERG65YA0"
Floating licenses are broken down into a HOST line, an ISV line, and one or more LICENSE lines:
HOST - The host line indicates which server may provide the floating licenses in the license file.
• <server_name>, also known as the hostname, is the name of the license server, for example red.
• <server host id>, also known as the rlmhostid or System ID, is a unique number for that machine.
• <port> is the user-defined server port number over which requests from the client are made to the RLM daemon.
ISV - The ISV line indicates which vendor made the license. The vendor line helps decode the license line for the Foundry's specific licensing keys and identify the vendor licensing daemon.
• <options file> is the plain text file that controls the behavior of the server. Specifying an options file in the license is optional.
• <port> is the user-defined port over which the vendor daemon communicates to the client. If left blank, the port number is picked for you.
Note: The host port number and the ISV port number MUST be different, and remember to avoid port 4102, which is reserved for the web server.
LICENSE - license feature line. The only difference from a node-locked license is that uncounted is replaced with the number of available floating licenses and the hostid in omitted from the LICENSE block.
The above license works on any 10 hosts simultaneously. It licenses all Mari releases built before 6 October 2012 and it begins 6 October 2012.
Client License Syntax
Client RLM licenses typically have just one line, which may be:
HOST <server name> <server host id> <port number>
or
HOST <server name> any <port number>
License Feature IDs
The Feature ID describes the product that the license is for and the type of license, either interactive (_i) or render (_r) and maintenance (maint). Interactive licenses grant you access to the interface of the product in question. Render licenses run in 'headless' mode, so you can only render existing scripts. Maintenance licenses grant you free product upgrades within the current release cycle allowing you to run the latest major and minor releases of the application to get access to new features and bug fixes.
The following Feature IDs are valid:
|
Feature ID |
Description |
Website |
|---|---|---|
|
3delight_r |
A render license for 3Delight as shipped with Katana 3.0 and later. |
|
|
flix_i |
An interactive license for Flix. |
|
|
foundry_production_i |
A collective interactive license for Nuke Studio, Modo, and Mari. |
|
|
foundry_creation_i |
A collective interactive license for Modo, Mari, and Hiero. |
|
|
hiero_i |
An interactive license for Hiero. |
|
|
hieroplayer_i |
An interactive license for HieroPlayer. |
|
|
katana_i |
An interactive license for Katana. |
|
|
katana_r |
A render license for Katana. |
|
|
mari_i |
An interactive license for Mari. |
|
|
mari_r |
A render license for Mari. |
|
|
marinc_i |
An interactive license for Mari Non-Commercial. Non-Commercial versions of software provide a sub-set of full product functionality. |
|
|
modo_i |
An interactive license for Modo. |
|
|
modonc_i |
An interactive license for Modo Non-Commercial. Non-Commercial versions of software provide a sub-set of full product functionality. |
|
|
nuke_i |
An interactive license for Nuke. |
|
|
nuke_r |
A render license for Nuke. |
|
|
nukenc_i |
An interactive license for Nuke Non-Commercial. Non-Commercial versions of software provide a sub-set of full product functionality. |
|
|
nukestudio_i |
An interactive license for Nuke Studio. |
|
|
nukex_i |
An interactive license for NukeX. |
|
|
nukexassist_i |
An interactive license for Nuke Assist. |
|
|
Nuke Plug-ins |
||
|
caravr_nuke_i |
An interactive license for CaraVR, providing that you already have a Nuke license. |
|
|
caravr_nuke_r |
A render license for CaraVR, providing that you already have a Nuke license. |
|
|
caravrmaint_nuke_i |
An interactive license for CaraVR including maintenance, providing that you already have a Nuke license. |
|
|
caravrmaint_nuke_r |
A render license for CaraVR including maintenance, providing that you already have a Nuke license. |
|
|
ocula_nuke_i |
An interactive license for Ocula, providing that you already have a Nuke license. |
|
|
ocula_nuke_r |
A render license for Ocula, providing that you already have a Nuke license. |
|
