Delta2D floating license server
Before you begin
Please choose the computer for the floating license server carefully. The computer should be available in the long term and has to run whenever someone wants to work with Delta2D. On the other side it doesn't have to be powerful, the Floating License Server is no heavy duty application.
Please note that in the default configuration the Floating License Server can manage floating licenses within the same subnet only.
Your subnet is defined by the so-called subnet mask. Contact your network administrator to learn which machines belong to the same subnet and which machine should be chosen as floating license server machine. Let us know if you face any difficulty with the subnet or need to make the floating license available outside the subnet.
Which Delta2D version do you want to install?
With Java 6 Update 19 changes in some crucial java functions were introduced. So you will have to take care to choose the Floating License Server with the Java version matching your Delta2D Java version. This means:
- Delta2D 4.1 and older needs Floating License Server with Java 1.6.0_18
- Starting with version 4.2, Delta2D needs Floating License Server with Java version 1.6.0_19 or newer
Replace the license
If you just want to update the Delta2D version you do not have to re-install the complete Floating License Server, but you will have to replace the license for the Floating License Server, since it includes a limit for the Delta2D version.
- Stop the Floating License Server:
under Microsoft Windows:
- open the windows services console by hitting the WINDOWS + R keys simultaously, enter "Services.msc" in the little window and click on the [OK] button
- Locate the service "DECODON Floating License Server" (or similar) and select it.
- Right-Click on the row and choose "Stop Service" from the menu
- In the installation directory replace the file
license.lfsby the new one:
- rename the old one (e.g. to
- insert the new license file
- rename the new license file to
license.lfs(in case you don't see any suffixes, only rename it to
- Start the Floating License Server again:
- Right-Click on the service entry again and choose "Start Service" from the context menu
You are done and can now use the updated Delta2D installations on the clients.
In Case of Upgrading from an old version (older than version 2010XXXXXXXX):
– Uninstall previous versions of the floating license server
- Open a console window and navigate to the installation directory of the floating license server
- There you can find a subfolder called
service. Cd into that directory:
- Stop the service by calling the script you can find there, under Windows type
wrapper_stop.bat, under Linux and Mac type
wrapper.sh stop. Check your list of processes that the Floating License Service is really stopped. You should not see any process called wrapper or java, if you see a java process, have a look at the details to make sure that it is not the license server.
- Now remove the service. Under Windows type:
wrapper-uninstall.bat. Under Linux remove the startup links from the runlevels where they were set.
- Finally you can remove (or rename) the complete directory
FloatingLicenseServerto make sure that a newer version of the floating license server is not installed into the same directory.
Install the floating license server
- Save the Installer file corresponding to your Operating System (see below) and the needed java version to your local machine.
- Make sure that you have your license file whithin reach
Installation under Windows
- Double click on the installer file you just downloaded to start installation
- The install wizard will guide you through the installation process, just follow the instructions
- At the end of the installation you will be asked for your license file; click on Browse..., navigate to your license file and continue with click on Next > to finish the installation.
- The Floating License Server is now installed as a service starting automatically at system startup, but if your license is not yet registered, it will not yet be usable until registration is accomplished. If your license already is registered to this computer, you are ready and can skip the following steps. Else please continue with Registering your License
Installation under Linux
- Under Linux you will have to make the downloaded file executable:
chmod +x FloatingLicenseServer-with-jre-1.6.0_22-for-linux.sh
- Now run the installer file from command line with
./FloatingLicenseServer-with-jre-1.6.0_22-for-linux.shand follow the instructions.
- Copy your license file into the installation directory:
cp license_xxxx_my_workgroup.lfs /opt/DECODON/FloatingLicenseServer/.(replace the file name by your own license file).
- If your license file is not yet registered, please proceed with Registering your License. Else you are done.
- To make the Floating License Service start automatically on system boot, please make the necessary links to
/etc/init.d/FloatingLicenseServiceinto the desired runlevels
Registering your License
- To register the Floating License Server start the Console application of the Floating License Server: Click on the Start menu:All Programs > DECODON Floating License Server > Floating License Server Console. Under Linux start
/opt/DECODON/FloatingLicenseServer/FloatingLicenseServerdirectly in the console.
- A new shell window will appear, displaying information and offering a the prompt ">". Type
copyand press ENTER. The Floating License Server will copy important registration information to the clipboard.
- Open an Email, paste the information (on Windows: use CTRL+V) into the email body and send the email to firstname.lastname@example.org.
- You will receive a registration key. Select it in the email body and copy it to the clipboard with CTRL+C.
- Insert the key in the Floating License Server shell window by typing
paste. Confirm with pressing ENTER.
- The Floating License Server is running now.
- You can stop the Floating License Server by typing
exitand confirming this with ENTER.
- Please restart the Floating License Service to apply the changes. In Windows you can use the start menu items Stop Service and Start Service to do this.
Control the Service:
The Floating License Server is now running as system service and you can control it via command line or with the Windows System Management: Open the Management Console, click Start/Run and then type
services.msc. There you can look for the "DECODON Floating License Server (dfls)". Like any other service you can start, stop, or restart this service with the controls on top of the window. Messages of the Floating License Server service can be found in the eventlog: Type
eventvwr.msc to open the event viewer.
On command line you can stop the service manually with the script
FloatingLicenseService-Stop.bat and start it with
Mac and Linux:
- The installation directory includes a file
FloatingLicenseService. It can be started with the following options:
Keep an eye on
/var/log/messages on Linux or the system log in the Console application on Mac OS X to track messages and warnings from the Floating License Server.
Firewalls between Delta2D and the Floating License Server need to allow the communication via TCP port 8888 and UDP port 5353:
The communication between Delta2D and the license server uses the TCP network protocol, via port 8888.
Usually Delta2D automatically discovers the floating license if it is running in the same subnet. The underlying technology for the discovery is Bonjour (a.k.a. Rendezvous, a.k.a. zeroconf). The bonjour / zeroconf technology sends UDP packets via port 5353.
Server: information requests via telnet
Connect to the server via telnet by typing the command
telnet [servername] [port]. You will not see any fancy response, just the bare fact that there is no failure message is sufficient to be sure that the connect succeded.
Then type in one of these options to check for the server status (depending upon your terminal configuration you might not be able to see what you type):
Confirm with ENTER.
The server will send a status response and interrupt the telnet connection after this request. This is the expected behaviour.