Commercial plugins for OpendTect are often protected by FlexNet licenses. The FlexNet system is based on text files with coded keys. Basically, before a certain action is done the plugin will request permission from the FlexNet system. FlexNet in turn consults the license file, and will contact a license manager daemon on a server if necessary.
The FlexNet licensing system allows a variety of licensing options. The most important license types are:
Demo and Node-locked licenses are the easiest to install but more difficult to maintain. Demo licenses because they are valid for a limited period of time, node-locked because they will only allow usage on one or more computers explicitly named in the license file. Node-locked licenses can be recognised by lines with the 'HOSTID=' in it, like:
FEATURE dTect dgbld 4.6000 1-jan-2014 uncounted 023E2CE466C7 \ HOSTID="00146c37f273 00167600d558"
Floating licenses are managed by a license server. When the plugin needs a license, FlexNet will contact this server machine. You have a floating license if the first actual line of the license file contains 'SERVER', like:
SERVER houserv001 00146d37ec2a
For a licensing scheme to work, there must be a unique identifier for the server or (in case of a node-locked license) the working computer. In most cases, this identification will be tied to the address of your network card. How to obtain this 'FlexNet Host ID' is dependent on the operating system. The different ways to obtain it are described in the host ID section of the 'FlexNet licenses explained' page.
Note that the FlexNet host ID is never the IP address of the computer.
It is possible to use, for example, a Linux server to give out licenses on Windows systems. In general, it doesn't matter what Operating system you have on your license server. The OpendTect program will take a look at the local license file and try to contact the host denoted in the 'SERVER' line. For this to work, the computer running OpendTect must be able to 'see' the license file. This can be done by putting the license file on a shared network disk, or putting a copy of the file on each computer.
Sometimes the server host name, as found in the SERVER line is unknown to the client computer (the computer running OpendTect). In that case you can simply edit the copy of the license file to match something that the client computer does understand. For example:
SERVER houserv001 00146d37ec2acan be changed in:
SERVER 18.104.22.168 00146d37ec2a
Note that you cannot change the host ID; that will invalidate the licenses.
When you obtain an upgrade for your current license file, then you have to make sure that:
Quite annoying is the problem of FlexNet 'helping' you by remebering the location of old license files and using those rather than new ones that you have specified. Therefore, it is usually a good idea to remove all old license files that you can find, or at least renaming them just so FlexNet cannot find them.
You can, at some point in time, be confronted with a firewall blocking communication between a client and the server computer. Before starting to change firewall settings, it may be interesting to know that you can specify the port that FlexNet uses to communicate through. This is done on the SERVER line, as follows:
SERVER houserv001 00146d37ec2a 54321
In the above case you specify that FlexNet needs to use port 54321, rather than the default 27000 (and up). Note that this needs to be done for both the server's and the client(s) license file(s).