|
|
 |
 |
|
 |
 |
|
Network Licenses are available to any of our users who are currently running 3 or more copies of Fusion, DFX+ or
DF Render Node at their facility for a fee of $195 US. If you are interested in converting your facility over to a network license setup, and meet
the required criteria then please feel free to contact us at  sales@eyeonline.com
When approved you will be issued a temporary network license, and will be asked to return all but one of your facility's
hardware dongles to eyeon. When these are returned a permanent network license will be issued. (The network license
setup requires one dongle for the computer acting as the license server.) Once you have received this file use the
instructions and files included below to set up your facility accordingly.
|
LMGRD.exe (v 9.2.0 | 644 Kb)
(version: 07/11/2003)
The license manager daemon (lmgrd) handles the initial contact with the client application programs, passing the
connection on to the appropriate vendor daemon. It also starts and restarts the vendor daemons.
EYEON.exe (1.2 Mb)
(version: 08/16/2005)
This is the eyeon daemon itself... Integral to running a network license scenario.
EXAMPLE.dat (emailed by eyeon Software)
This is your network license file that will be issued and emailed to you by eyeon Software. You can rename it whatever you
need but must not rename it when the license manager is active.
|
|
LMTOOLS.exe (v 9.2.0 | 744 Kb)
(version: 07/11/2003)
This file allows a more GUI approach to running the license server, as well as allowing the license server to be run
as a Windows service.
Globetrotter User Manual (PDF | 1.3 Mb)
This is the Globetrotter FLEXLm Network License manual, and it explains the basics of network licensing as well as
providing in-depth information on the tools provided above. Highly recommended to have on hand.
*
All Files (ZIP | 1.4 Mb)
All of the seperate files available on this page (except the license file) included in a single zip. Requires only a
single file to be downloaded.
|
|
 |
Installing the License Server |
 |
|
After contacting eyeon Software to switch to network licenses you will be asked to set aside one of your existing
dongles. (Or you may be shipped a new dongle if you are currently not running Fusion.) This dongle needs to be
connected to the back of the computer chosen to act as the license server. Ensure that this machine is either running
Windows NT, Windows 2000 or Windows XP.
Note: If Fusion has never been installed on this machine, you will need to install the HASP drivers so that the hardware lock
can be read by the license server. You can download the installer for the HASP drivers from our
Downloads>General Utilities section.
Copy or save eyeon.exe, lmgrd.exe, lmtools.exe and your EXAMPLE.dat file into a directory. We usually recommend creating a directory
on the root of C: to put these files in a folder named FlexLM (C:\FlexLM) but any directory could be used.
Open the EXAMPLE.dat license file, and modify the first line. Replace the word SERVERNAME with the actual network
name of your license server. Save the file. (Note: SERVERNAME is the only variable that can be modified by you.
Everything else must be left as is.) This must be the name that all of the Fusion/DFX+/Node machines see this computer
as across the network.
Once you have saved the license file and any changes you have made, you will need to run the license server.
From the command prompt, navigate to the FlexLM folder (or different depending on where you placed the files) and run
the following command.
C:\FlexLM>lmgrd -c EXAMPLE.dat (or whatever the license file is named)
Once you have done this the license server will be running and the status of the server will be indicated in the log it
maintains. This log file, which is actually a simple text file documenting all licenses checked in and out will be
automatically created in your C:\FlexLM folder (or where ever those files sit)
|
|
|
Setting up the Client Workstations |
|
|
On each workstation that will access the license server rather than a dongle you will need to install
the particular version of the software (at least version 3.1 to support network licenses) you intend to use on it.
Once the software has been installed it will still ask for a dongle until you add an environment variable
to the
system, EYEON_LICENSE_FILE, with a value of @SERVERNAME; where SERVERNAME is the name of your license server as seen by the
workstations across the network.
(an IP address is also acceptable, such as @192.168.0.21;. Don't forget the semicolon at the end!)
To add an Environment Variable, go to the Start>Settings>Control Panel, and then to System and open the
Advanced Tab.
Then click on the button labelled Environment Variables. In the window that opens, click on the New button under
the 'System Variables' section and configure the new variable with the values indicated above.
Once everything has been setup you will be able to run Fusion/DFX+/Render Node on any machine properly configured on
your network, without the worry of having to swap and maintain several dongles.
|
|
|
Setting Up as a Windows Service |
|
|
The chances are that you will want to install the FlexLM license server as a
Windows service after you have confirmed that everything is working properly. By
installing the license server as a service you will be able to ensure that the
license server is always available when the computer is running, even when
no one is logged in to the machine.
The lmtools.exe application makes it very easy to configure your license
server as a service. Start lmtools.exe, and select "Configuration Using
Services" from the radio button options in the "Service/License File" tab.
Now switch to the "Config Services" tab, and note the controls that appear.
The first is a drop down menu labelled Service Name. Unlike many drop down
menus you can edit the contents of this control.
The default value of 'FlexLM Service 1' is pretty uninformative, to change this simply click in
the control area and type in a new, more descriptive name. I suggest 'eyeon
FlexLM License Server'.
Once you have entered the new name look at the next control, labelled "Path
to the lmgrd.exe file". Click on the browse button to the left of the
control to browse to the location of the lmgrd.exe file you use with
Fusion's license server, or type the path in manually.
The next control requires a path to the license file on disk. The browse
button will display a dialog that defaults to showing only files with the
*.lic extension. Click on the files of type menu and select *.dat to show
the license files used by Fusion.
The third control requires the path and name of the file to use for the log
that is written by the service as it runs. This file contains all of the
information you would normally see when you are running the license server
from the console. Please note that the file does not have to exist already, it
will be created automatically when the license server service starts.
Now select the "Use Services" checkbox, and if you want the license manager
service to start everytime the computer starts enable the checkbox labelled
"Start Server at Powerup".
When all of these controls are set, select the "Save Service" button at the
top of the screen. The service will be installed into Windows, and will
start the next time you restart your computer.
A reboot is not required however, to start your server for the first time, simply
open the Start > Settings > Control Panel > Administrative Tools > Services window.
You can use the options and settings you find here to start your service for
the first time.
|
Another issue that might arise for your facility when converting over to network licenses involves unique serial
numbers for your copies of Fusion. When running DF tied to a dongle, the serial number for that copy of the
software is the serial number encoded to the dongle. When running DF off of a license server, there is by default
no unique serial number for each copy of the program that is launched. This is not a problem for Fusion though, but does
become an issue for certain third-party plugins that rely on a unique serial number for licensing purposes.
To get around this a network license file can be encoded with serial number routing, which will assign a set of unique
pre-defined serial numbers to each copy of DF running on the network based on the systems IP address. In the license file
itself the IP addresses that are automatically assigned can be modified by the user in order to match the IP addresses
used on the facitities network.
If you need a network license with serial number routing or already have a network license and need the routing enabled
please contact technical support at tech@eyeonline.com
|
|
|
|
|
|
|
 |
 |
|
 |
|